Payments · Field Guide
Payment Method
The provider-supported payment type the customer chooses for the current transaction.
Why LAWNSNOWAPP asks for it
Card and bank payments require different secure fields, eligibility checks, disclosures, and merchant-side processor-cost schedules.
How LAWNSNOWAPP uses it
In the enabled TEST MODE flow, LAWNSNOWAPP tokenizes through the secure provider form, uses the contracted merchant processing schedule for that method, and keeps that merchant processor cost separate from the customer invoice.
Example
Choose ACH to enter bank details in the secure bank form, or Card to use the provider-hosted card fields.
If you leave it blank
The payment cannot proceed until a supported method and its required secure fields are complete.
If you change it later
Changing the method resets the secure payment entry before authorization; it does not alter the invoice's stored amount.
Financial, compliance, or safety note
The payment provider handles the sensitive credential. Merchant processor pricing and the LAWNSNOWAPP platform fee are different concepts. MVP flat-rate pricing does not add a customer surcharge.
Common mistakes
- Putting card or bank data into ordinary notes
- Treating merchant processor cost as a customer invoice fee
- Assuming a TEST MODE control is a live production payment