Payments Overview

SuperApp supports the full spread of how customers actually pay: online cards and digital wallets, cash and cards at handover, and a built-in marketplace wallet. You choose which methods your marketplace offers, configure them once, and the platform handles authorization, collection tracking, and refund routing consistently across every vertical.

Online payments

Stripe — the primary gateway

Stripe is the primary online gateway, giving you:

Card payments with saved cards for returning customers.
Apple Pay and Google Pay for one-tap checkout on mobile and web.
3-D Secure authentication where banks or regulations require it, handled within the checkout flow.
Secure, PCI-compliant processing — card details never touch your marketplace’s systems.

Additional regional gateways

Beyond Stripe, additional regional gateways are available so you can offer the payment rails your market expects. Gateway availability varies by region — your SuperApp team will advise on the right setup for your market. Configuration is covered in Gateway setup.

You can enable more than one gateway; each payment method customers see maps to the gateway that processes it, and you can switch which providers are active without disrupting saved customer experiences.

Physical payment methods

For orders paid at handover rather than at checkout:

Method	How it works
Cash	Customer pays cash on delivery or at pickup; the merchant or driver records collection.
Card on delivery	Customer pays by card at the door using the driver’s/merchant’s own card machine.
Card terminal	Customer pays on a card terminal at the outlet (pickup and dine-in).
Bank transfer	Customer pays by bank transfer, with the payment reconciled against the order.

Each method is individually toggleable, so your marketplace offers exactly the set that fits your market. Every method — online or physical — is an entry in Payment Config (/configuration/payments/payment/list) with its own display Name, Priority in the checkout list, visibility, conditions (such as restricting by order type or amount), and optional per-method Fee, Cashback, or Reward Points — see Commission & charges for the fee side.

Physical payments are tracked through the order lifecycle — staff record collection as part of completing the order, so reporting stays accurate.

The marketplace wallet

The wallet is a store-of-value account each customer holds inside your marketplace:

Customers can pay with wallet balance at checkout — full or partial, with the remainder on another method.
Refunds can be credited to the wallet instantly, which customers often prefer to waiting on a card refund.
Wallet credits double as a growth tool: cashback, promotional credits, and goodwill gestures all land in the wallet and come back to you as orders.

Wallet configuration and growth mechanics are covered in Wallet.

How refunds are routed

Refunds — from cancellations, order edits, or goodwill — follow configurable routing:

Back to the original payment method — an online payment is refunded through its gateway to the customer’s card or digital wallet.
To the marketplace wallet — instant credit the customer can spend on the next order. This can be the chosen method, or a configured fallback when a gateway refund isn’t possible (for example, a cash order being refunded remotely).
Physical refund methods — cash or bank transfer, recorded by staff, for marketplaces that operate that way.

You control which refund methods are allowed, the default, whether refunds process automatically in cancellation and edit flows, and whether large refunds require an extra confirmation step. Role permissions determine which staff can process refunds at all. Refunds that are approved but not yet completed are listed under Dashboard → Reports → Pending Refunds (/reports/pending-refunds).

Tips

Customer tipping is supported at checkout with configurable suggested amounts, and tips flow through to driver earnings reporting.

Security and compliance

Online payments are processed by the gateways themselves (PCI DSS-compliant providers); your marketplace never stores raw card numbers.
3-D Secure / strong customer authentication is supported where required.
Payment activity is tracked per order, so every collection and refund is auditable in reports — the payment-wise report (/reports/payment-wise) breaks volume and totals down per payment method.

What to configure, in order

Connect your gateway(s) — Gateway setup.
Enable physical methods your market uses.
Decide wallet policy — enabled? refund destination? fallback? — Wallet.
Set refund rules — allowed methods, defaults, auto-processing, large-refund confirmation.
Configure commission, taxes, and charges — Commission & charges.
Set up settlements so merchants and drivers get paid — Settlements.
Test end to end with a real small payment and a real refund before launch.

Practical guidance

Offer cash where cash is king. In many markets, cash on delivery is the difference between mainstream adoption and a niche app — the platform tracks it properly, so there’s little downside.
Enable wallet refunds even if you don’t push the wallet. Instant refund credit resolves complaints faster than any gateway refund timeline.
Keep the method list short. Every method you enable is a method your merchants and support team must handle; add methods deliberately.

Gateway setup · Commission & charges · Settlements
Wallet — the wallet as a growth tool
Editing & refunds · Cancellations