Payments that clear, reconcile and refund without a spreadsheet

mada is the national debit network, and in practice a Saudi checkout without it loses sales. Cards from international networks come next, protected by 3-D Secure authentication. Apple Pay is widely used on iPhones and cuts checkout to a touch. Buy-now-pay-later providers like Tamara and Tabby let shoppers split larger baskets, and for fashion, electronics and home goods they often raise average order value.

Each method has its own rules. Some providers bundle mada, cards and Apple Pay behind one integration; BNPL providers typically have a separate API and their own approval process. Settlement times and fees vary by method, and some methods support recurring payments while others do not. We lay these differences out in a one-page comparison so you choose with the numbers in front of you.

We also look at where each method appears in the journey. BNPL messaging belongs on the product page and in the cart, not only at the final step. Apple Pay works best as an express option high in the checkout. Small placement choices move conversion more than most visual changes.

The browser is not a reliable witness. Customers close tabs, networks drop, and redirects fail. So every integration we build treats the provider's server-to-server webhook as the source of truth. We verify the webhook signature, process it exactly once using idempotency keys, and retry safely when your system is briefly down.

Card data should never touch your servers. We use the provider's hosted fields or hosted payment page, which keeps your exposure to card-data security requirements small. We follow OWASP guidance for the surrounding code: input validation, secret storage, rate limits and audit logs on every payment action.

Then comes the unglamorous part that finance cares about. Refunds, partial refunds, cancelled authorizations, chargebacks and settlement batches are all modelled. We produce a reconciliation report that matches each payout to its orders, separates provider fees, and flags anything that does not add up. That report is what lets your accountant close the month without chasing screenshots.

Online payments in the Kingdom run through providers operating under the oversight of the Saudi Central Bank (SAMA). We do not hold funds or process cards ourselves. We integrate licensed providers into your product, and your merchant agreement is with them. Always confirm a provider's licensing status with the provider and with SAMA's published information before you sign.

Onboarding takes time, usually a few weeks, and it needs documents such as your commercial registration, bank details and a working website with clear refund and delivery terms. We prepare the technical parts of the application and build against the sandbox in parallel, so integration is finished when approval lands.

Payments also feed tax records. For VAT-registered merchants, a successful payment should trigger an invoice in the structure ZATCA e-invoicing requires, and a refund should produce a credit note. We connect the payment events to your invoicing solution or ERP, so the sales record, the bank record and the tax record agree. For store builds, see our Shopify and Salla and Zid services.