Taking payment in person

The money panel is on the visit, so taking payment is something that happens where the work happened rather than back at the office three days later.

Tap to Pay

With your Stripe account linked, the phone is the terminal: Tap to Pay on supported iPhones, NFC on supported Androids. The customer taps their card or their phone against yours.

The division of labour is deliberate: the server sets the amount, the phone collects the card, and the ledger settles from Stripe's answer — so a phone that dies mid-tap cannot leave you with a payment that happened and a record that does not know about it.

The hosted card page

No tap — an older phone, a card that will not read, a customer who would rather type it? Open the hosted Stripe Checkout card page on the phone. It is the same page a payment link opens. The customer enters their card there, and the card number goes straight to Stripe — it never touches this app.

Tap to Pay and card entry are offered independently of each other. The server advertises each on its own and the app renders exactly what it is told, rather than guessing at what the device can do and quietly hiding the option that would have worked.

Cash, checks and everything else

This needs no payment account at all, and that is the point rather than a consolation prize. Record cash, a check, a bank transfer, or any method your company has defined, and refund them later if you need to.

Tips

Where your company has switched tips on for the working location, every in-person flow asks once, up front: preset percentages with their real amounts shown, a typed amount, or no tip. The tip goes to the server, which owns the arithmetic, and the ledger row afterwards says "includes … tip". See Tips, fees and refunds.

The other two ways

From the same panel you can also charge the card on file, or email a payment link — for the customer who wants to pay later, or who is not there.