Gateway setup

Payment configuration has two halves, and keeping them straight makes everything else simpler.

Screen	Controls
Payment Provider	The gateway accounts — credentials, enable/disable, connection testing
Payment Config	What customers see at checkout — names, order, conditions, fees

Disabling a gateway in Payment Provider is a provider-level kill switch: every method that runs through it stops being offered, without touching the rest of your setup.

Where to find it

Dashboard → Finance → Payments → Payment Provider (/configuration/payments/payment/payment-gateway-list) — Admin, Co-Admin

The methods customers see are next door at Payment Config (/configuration/payments/payment/list).

Before you start

• An admin login.
• A gateway account for your business. Stripe is the usual choice; Finix, Paytrail, InterGateway and Banca Transilvania are supported where they suit the market better, and your account team configures those with you.
• The account fully activated for live payments. Gateways verify a business before releasing live processing; test payments work before that, real ones do not.

Connect the gateway

1. Open Payment Provider and add your gateway.

2. Enter the credentials from the gateway’s own dashboard. Use test keys first if you want to dry-run, then switch to live keys for launch.

3. Test Connection — this confirms the credentials are valid and the account is reachable.

4. Enable the gateway so its methods can appear at checkout.

5. Register the webhook the gateway needs, and paste its signing secret back here. Without it, payments succeed at the gateway and never confirm on the order — see Webhooks & the menu API.

Test keys versus live keys

Test keys accept only the gateway’s test cards and move no real money; live keys charge real cards. Launching on test keys means every real customer’s payment fails, and the failure looks like a platform problem rather than a configuration one. The checklist below exists for this.

Apple Pay and Google Pay

Once a gateway is connected, both can be offered in the app and on web ordering, processing through the same account. Device-wallet registration is handled as part of app setup — you confirm you want them, your account team does the registration.

Build the checkout list

Each entry under Payment Config is one thing a customer can choose. The full field list is in Payments overview; the decisions that matter here are:

• Which methods you actually accept, and in what priority order.
• Conditions — this is how you require prepayment for delivery while allowing cash for pickup, or keep a method to one outlet. There is no separate per-outlet payment screen.
• Fees, cashback and points, if you want to steer customers toward one method — see Taxes & charges.

Disabling a method removes it from checkout immediately. A customer who had it saved is simply asked to pick another next time; nothing breaks.

Go-live checklist

1. Live credentials in place, not test ones.
2. Test Connection passes.
3. A real card, a real order — small, and confirm it shows as paid and appears in the gateway dashboard.
4. Apple Pay and Google Pay, one order each on a real device, if enabled.
5. A refund of that test order, confirmed at the gateway. See Refunds & disputes.
6. The method list reviewed — only what you accept, in the order you want.
7. Taxes and charges verified on the test order, line by line.
8. Payout schedule confirmed in the gateway dashboard, so you know when money actually lands.

Day to day

• Watch the gateway dashboard for payouts, disputes and chargebacks. Disputes are answered there, not here.
• Rotating credentials — update them here in the same session and re-run Test Connection. Old keys stop working the moment they are rolled, and so does the webhook secret.
• Reconcile using the payment-wise report (/reports/payment-wise) against your gateway’s payouts.

Troubleshooting

Symptom	Likely cause
Every card payment fails	Test keys in live use, or the account is not activated
Test Connection fails	Mistyped or rotated credentials
Payments succeed at the gateway but orders never confirm	The webhook is not registered, or its secret is wrong
A method is missing at checkout	It is not public, its conditions exclude the order, or its gateway is disabled
The Apple Pay button is missing	Wallet registration incomplete, or an unsupported device
A refund is not arriving	Card refunds take several business days; check the gateway and /reports/pending-refunds

Related: Payments overview · Taxes & charges · Refunds & disputes · Webhooks & the menu API