Gateway Setup

Gateway setup is where you connect your marketplace’s online payment providers — Stripe as the primary gateway (cards, Apple Pay, Google Pay, 3-D Secure), plus any regional gateways your market needs — and control which payment methods customers actually see at checkout. Gateways and payment methods are configured separately, which is what makes the system flexible: one connected gateway can power several customer-facing methods, each with its own visibility rules and fees.

The two halves of payment configuration

Screen	What it controls
Payment Provider	The gateway accounts themselves — credentials, enable/disable per provider, connection testing
Payment Config	The list of payment methods customers see at checkout — display name, ordering, visibility, conditions, per-method fees

Disabling a gateway in Payment Provider acts as a provider-level kill switch: every method that processes through it stops being offered, without touching the rest of your payment configuration.

Connect Stripe

Create or sign in to your Stripe account at stripe.com. Live payments require the account to be fully activated (Stripe verifies your business and bank details first).
In the dashboard, open Dashboard → Settings → Payment → Payment Provider (/configuration/payments/payment/payment-gateway-list).
Add Stripe and enter the API credentials from your Stripe dashboard. Use test keys first to dry-run with Stripe’s test cards, then switch to live keys for launch.
Use Test Connection to verify the platform can reach your Stripe account with the saved credentials.
Enable the gateway.

Apple Pay, Google Pay, and 3-D Secure

Once Stripe is connected, Apple Pay and Google Pay can be offered in the customer app and web ordering, processing through the same Stripe account — your SuperApp team handles the device-wallet registration during onboarding. 3-D Secure (bank verification, required in many regions) is handled inside the checkout flow automatically.

Regional gateways

Where Stripe isn’t available or isn’t preferred, additional regional gateways are supported. These are configured together with your SuperApp team during onboarding — contact them with your market and they’ll set up the right provider in Payment Provider alongside (or instead of) Stripe.

Configure the methods customers see

With a gateway connected, build the checkout method list under Dashboard → Settings → Payment → Payment Config (/configuration/payments/payment/list). Each entry is one method customers can choose, with:

Internal Name and a Payment Method selection (which underlying method/gateway it maps to)
Display Name and Description — what customers read at checkout
Priority — sort order in the checkout list
Visibility — Public, Private, Info
Feature toggles — Is Wallet Top-up, Is Wallet Auto Top-up, Is Membership Payment, Is Exclude Order
A conditions builder — restrict a method by order type, order amount, and similar rules
Optional per-method Fee (fixed + percentage, with a maximum), Cashback, and Reward Points

Physical methods — cash, card on delivery, card terminal, bank transfer — are configured here too; they don’t need a gateway, just an entry so they appear at checkout. Per-method fees and cashback are covered in more depth in Commission & charges.

Per-outlet payment methods

Individual outlets can carry their own payment method setup under Dashboard → Outlets → (outlet) → Payment (/outlet/manage/:outletID/payment/list) — useful when one merchant takes card terminal payments and another is cash-only.

Go-live checklist

Live keys in place — the gateway holds live (not test) credentials.
Test Connection passes in Payment Provider.
Real-card test order — place a small order with a real card; confirm it shows as paid on the order and the charge appears in your Stripe dashboard.
Apple Pay / Google Pay test — one order with each on a real device, if enabled.
Refund test — refund the test order and confirm it lands in Stripe. See Editing & refunds.
Method list reviewed — only methods you intend to support are Public, in the priority order you want.
Per-method fees verified — if you charge method fees, a test order shows them correctly. Check the payment-wise report (/reports/payment-wise) after a few test orders.

Day-to-day management

Watch the gateway dashboard (Stripe or regional) for payouts, disputes, and chargebacks — disputes are answered through the gateway, not the platform.
Rotating keys — if you regenerate gateway credentials, update them in Payment Provider immediately and re-run Test Connection; old keys stop working the moment they’re rolled.
Disabling a method vs a gateway — to retire one method, switch off its Payment Config entry; to cut a whole provider, disable it in Payment Provider. Customers who had a removed method saved as a preference are simply prompted to pick another at their next checkout.

Troubleshooting

Symptom	Likely cause	Fix
Every card payment fails	Test keys in production, or Stripe account not activated	Switch to live keys; complete Stripe activation
Test Connection fails	Mistyped or rotated credentials	Re-copy keys from the gateway dashboard, save, re-test
A method doesn’t appear at checkout	Entry not Public, conditions exclude the order, or its gateway is disabled	Check the Payment Config entry and the gateway status in Payment Provider
Apple Pay button missing	Wallet registration incomplete, or unsupported device	Confirm wallet setup with your SuperApp team
Refund not arriving	Bank processing time	Card refunds typically take several business days; check status in the gateway dashboard, and see `/reports/pending-refunds` for refunds still in flight