The Payment methods tab on Payment settings controls the list of payment methods customers and staff see at checkout. Use it to add custom methods (bank transfer, cash, invoice, anything), enable each method independently for internal payments and the public booking site, and pick whether the methods show as a dropdown or button group.
Getting started
Navigate to Purchases > Payment settings and pick the Payment methods tab.
How it works
Your group ships with a default payment method that can't be deleted or renamed (it's the in-app card processor connected to your active gateway). On top of that, you can add as many custom methods as you want for offline or alternative payment types.
Each method has two independent availability flags: Activate on internal payments (your team can use it inside the console) and Activate on booking site (customers can pick it on the public booking page). A custom method can be active in one place and inactive in the other.
The layout selector at the bottom of the tab decides how the methods render to customers: a single dropdown menu or a row of buttons.
Step-by-step guide
Add a custom payment method
Click Add custom payment method at the top of the tab. The Create custom payment modal opens.
| Field | What it does |
|---|---|
| Payment method name | The label customers and staff see (e.g., "Bank transfer", "Cash", "Invoice") |
| Payment method content | Rich text editor for instructions or details. Renders in the customer flow when they pick this method (e.g., bank account info, deposit instructions) |
| Activate on internal payments | When on, your team can pick the method inside the console |
| Activate on booking site | When on, customers can pick the method on the public booking site |
| Mark booking site payments as unpaid | Renders only when Activate on booking site is on. When on, payments using this method are marked as unpaid until you manually confirm receipt |
Click Save to create the method, or Cancel to discard.
The Mark booking site payments as unpaid toggle is useful for methods like bank transfer where the customer "pays" but you need to verify receipt before the booking is confirmed. The transaction stays in Pending payment status until your team marks it as paid.
Reorder payment methods
Grab the drag handle (left side icon) on any method row and drag it to a new position. The new order saves automatically. The order on this list controls the order customers see when they pick a payment method.
Edit, deactivate, or delete a method
Click the three-dot menu on the method's row.
| Action | When | Effect |
|---|---|---|
| Edit payment method | Custom methods only | Reopens the modal with the current values prefilled |
| Activate on internal payments | When currently inactive internally | Enables the method for staff use |
| Deactivate on internal payments | When currently active internally | Hides the method from your team's payment flow |
| Activate on booking site | When currently inactive externally | Enables the method on the public site |
| Deactivate on booking site | When currently active externally | Hides the method from customers |
| Delete payment method | Custom methods only | Removes the method permanently. Past transactions that used the method are unaffected |
The default payment method has no Edit or Delete options; only the activation toggles apply.
Change the layout
Scroll to the bottom of the tab and pick a value from the Payment method layout dropdown.
| Layout | What it does |
|---|---|
| dropdown | Renders methods as a compact select menu. Best when you have many methods |
| buttons | Renders methods as a row of clickable buttons. Best when you have a few methods and want them prominent |
Save your changes
Click Save settings at the bottom of the tab. This commits the layout change and any other tab-level settings. The drag-reorder of the methods list saves automatically as you drag, so it doesn't need this button.
Reference
Top-of-tab controls
| Control | What it does |
|---|---|
| Add custom payment method | Opens the create modal |
Methods list table
| Column | What it shows |
|---|---|
| Drag handle | Reorder by dragging |
| Supported payment methods | Method name. default badge on the built-in method |
| Available on internal payments | Green check icon when on, red X when off |
| Available on booking site | Green check icon when on, red X when off |
| Actions | Three-dot dropdown |
Per-row actions
| Action | When |
|---|---|
| Edit payment method | Custom method, opens modal |
| Activate on internal payments | Currently inactive internally |
| Deactivate on internal payments | Currently active internally |
| Activate on booking site | Currently inactive externally and method allows external |
| Deactivate on booking site | Currently active externally |
| Delete payment method | Custom method only |
Custom payment method modal
| Field | Type | Notes |
|---|---|---|
| Payment method name | Text input | Required, e.g., "Bank Transfer" |
| Payment method content | Rich text editor | Customer-facing instructions when method is picked. 200px height, basic toolbar |
| Activate on internal payments | Toggle | |
| Activate on booking site | Toggle | |
| Mark booking site payments as unpaid | Toggle | Conditional — renders only when Activate on booking site is on |
Layout selector
| Option | Description |
|---|---|
| dropdown | Compact select menu |
| buttons | Visual button group |
Save buttons
| Button | What it commits |
|---|---|
| Save settings (bottom of tab) | Layout selector and any other tab-level changes |
| Save (modal) | Custom method create/edit |
| Drag handle | Reorder saves automatically |
Good to know
- The default method can't be deleted or renamed. It represents your active payment gateway. To change it, switch gateways in Payment gateways.
- Custom methods work for any non-card payment. Use them for bank transfers, cash on arrival, mailed checks, invoiced billing, in-person manual processing, anything.
- Mark booking site payments as unpaid is your verification gate. Without it, the transaction reads as paid the moment the customer picks the method, which is wrong for methods like bank transfer where the money hasn't actually arrived yet.
- Independent activation means a method can be available internally but hidden from customers, or vice versa. Use this for staff-only methods (e.g., comp/test payments) or customer-only methods (e.g., a specific online wallet).
- Rich text content renders to the customer when they pick the method on the booking site. Use it to surface bank details, payment instructions, or anything else the customer needs to know.
- Reorder via drag is permanent and instant. No save button needed for the reorder itself — drag and drop persists immediately.
- Deactivating a method preserves transaction history. Past orders that used the method keep their references; only future selections are affected.
- Layout changes apply globally to your booking site. There's no per-event layout override.
FAQ
Q: Can I have a payment method that's only available internally?
A: Yes. On the create modal, toggle on Activate on internal payments and leave Activate on booking site off. Your team can pick it from internal payment flows; customers will never see it.
Q: What does the layout setting actually change?
A: It changes how customers see the payment-method picker on the booking site checkout. Buttons is best with a small number of methods (2–5) where you want each option prominent. Dropdown is best with many methods (6+) to keep the page tidy.
Q: Can I rename the default payment method?
A: No. The default method's name is determined by the active gateway. If you want a different label, the closest workaround is to set up the same payment as a custom method with the desired name and Mark booking site payments as unpaid off (so it acts identically to a paid order on the customer side), and turn off Activate on internal payments / booking site on the default method.
Q: Why don't I see the Mark booking site payments as unpaid toggle?
A: It only appears once Activate on booking site is on. Toggle the booking site availability first, then the unpaid-marker toggle appears.
Q: A custom payment method I created shows as "paid" in the transaction list, but the customer hasn't actually paid me. What did I miss?
A: Turn on Mark booking site payments as unpaid for that method. With it off, the transaction is treated as fully paid as soon as the customer picks the method. With it on, the transaction stays unpaid until your team marks the payment received.
Q: Can I delete the default method to clean up my list?
A: No. The default method is locked. Use Deactivate on internal payments and Deactivate on booking site to hide it from both surfaces if you don't want it visible anywhere.
Q: I deleted a custom method, but transactions that used it still reference it. Is that a bug?
A: No, that's intentional. Transactions reference the method that was active at the time of payment. Deleting the method doesn't remove the historical reference; it just stops you from picking the method on new orders.
Q: Will dragging a method to the top of the list change which method is selected by default?
A: The first method on the list is the default selection in the customer flow. Drag a method to the top to make it the default for new transactions.