Techbanq

Software · mada acceptance

Accepting mada is an architecture decision wearing a checkout button

For a Saudi customer base, mada is the card in most wallets, so the checkout must carry it well. The decisions that matter are made before the button exists: where card data flows and therefore how much of your estate PCI DSS assessment reaches, how tokens replace card numbers, how 3-D Secure challenges are handled, and what the scheme and your acquirer permit for recurring charges.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Shoppers moving through a modern retail concourse

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The decision order

Why the mada checkout is designed before the gateway is chosen

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

Teams usually start by shortlisting gateways, which is backwards. The prior question is architectural: where will card data be entered, and what will it pass through? The answer determines how much of your estate a PCI DSS assessment reaches, which is a multi-year cost, and it constrains everything after — which tokenisation you rely on, how a 3-D Secure challenge appears to your customer, and how much of the checkout experience you control. Choose the data flow first and the gateway shortlist writes itself; choose the gateway first and you inherit a data flow someone else decided.

The second early question is recurring payments. What stored-credential and recurring arrangements are supported for mada is defined by the scheme and by what your acquirer and gateway offer — and it is not safe to assume it mirrors what teams know from international card schemes. A subscription product should confirm those constraints in writing before its billing model is designed, because discovering them after launch means redesigning the commercial product, not just the code.

The three models

Three ways card data can flow through a mada checkout

Every checkout is one of these three, whether the team chose it or not. The scope consequences are the engineering view of PCI DSS — your formal obligations are assessed for your organisation, and your acquirer and assessor have the final word.

OptionWhere card data is enteredReach of assessment into your estateControl over the experienceEffort to build and maintainBest for
Hosted payment pageOn the gateway’s page, reached by redirect or frame; card data never enters your systems.The smallest engineering surface — your systems handle tokens and results, not card numbers.Limited; the payment step looks and behaves as the gateway built it.Lowest, and lowest to keep current as requirements evolve.Teams that want payments accepted with the least surface to defend.
Embedded gateway fieldsInside your page or app, but captured by the gateway’s components, which tokenise before anything reaches you.Moderate — your front end participates, your servers still never hold card numbers.High; the checkout looks native while the sensitive capture stays the gateway’s.Moderate, including keeping the components current.Products where checkout experience is part of the brand and the team can own more.
Direct API integrationIn your interface, passing through your servers before the gateway.The widest — systems that touch card data sit squarely inside the most demanding assessment territory.Total, over every pixel and every retry.Highest by far, in build and in permanent operational discipline.The rare case with a genuine need that the other two models cannot meet — and the appetite to carry what it costs.

What moves the effort

The four drivers of engineering effort in a mada acceptance build

No two checkouts cost the same, and the difference is rarely the button. These are the variables that actually move the work.

VariableEffect on priceWhy
The data-flow model chosenSets the baseline for everything elseHosted, embedded or direct decides how much sensitive surface you build and then defend for as long as the checkout lives.
3-D Secure across real devicesMultiplies the paths to testChallenge flows behave differently across browsers, in-app webviews and redirects; every path a customer can take is a path that must be built and rehearsed, including the abandoned challenge.
Recurring and stored credentialsCan reshape the product, not just the codeWhat the scheme and your acquirer support for stored-credential and recurring charges has to be confirmed early; a subscription model designed against assumptions imported from other schemes may need commercial redesign.
Reconciliation depthDecides whether finance trusts the numbersMatching gateway settlement reports to orders, captures, refunds and bank credits is its own subsystem; skipping it leaves the payment integration finished and the finance question unanswered.

Ask any supplier quoting this

  • Which mada flows does your gateway support in an embedded model, and what exactly do your components tokenise?
  • What stored-credential and recurring arrangements are available for mada on your platform, in writing?
  • What settlement reporting do you provide, at what cadence, and with which keys for matching to orders?

Our role

What we build for mada acceptance and what your acquirer decides

  1. 01

    The architecture, chosen deliberately

    We put the data-flow decision on the table with its scope consequences spelt out, so the checkout’s multi-year cost is chosen by you rather than inherited from a default.

  2. 02

    The checkout, built and rehearsed

    Tokenisation, 3-D Secure paths, failure states and retries are built and tested across the browsers and app contexts your customers actually use, not just the one on the developer’s desk.

  3. 03

    The reconciliation, made routine

    Settlement reports are matched to orders and bank credits as a built subsystem, so the payments your product takes are payments your finance team can explain.

Acquiring agreements, scheme participation, fees and the formal assessment of your compliance are between your organisation, your acquirer, your gateway and your assessor; we engineer the checkout so that what they assess is as small and as well-built as the product allows.

Common questions

What buyers ask

Does using a hosted payment page mean we can ignore PCI DSS?+

No — it means your obligations become much lighter to meet, which is different. A hosted page keeps card numbers out of your systems, which dramatically reduces the surface an assessment examines, but the merchant still has obligations: the integrity of the page that redirects, the handling of tokens and results, and the formal validation your acquirer requires for your organisation. We design for the smallest defensible surface and say plainly that scope reduction is an engineering outcome; what your compliance obligations are, and whether you meet them, is assessed for your organisation by the parties entitled to assess it.

Can we run subscriptions charged to mada cards?+

Confirm before you design, because this is where imported assumptions hurt. What stored-credential and recurring arrangements are supported for the domestic scheme is defined by the scheme’s rules and by what your acquirer and gateway actually offer, and it does not necessarily mirror what a team knows from international card schemes. The disciplined sequence is to get your gateway’s answer in writing, then design the billing model around it — which may mean adapting how renewals are charged or offering an alternative payment method for the recurring leg. Discovering the constraint after the subscription product has launched is a commercial redesign, not a patch.

Which payment gateway should we choose for mada acceptance?+

We will not hand you a ranked list, because the right answer is a function of your product, and a list flatters whoever compiled it. What we do is derive the criteria from your build: which data-flow model you chose, whether your recurring needs are supported in writing, how the gateway’s components behave inside your actual front end, what its settlement reporting gives your reconciliation to match on, and how its sandbox lets you rehearse 3-D Secure failure paths. Run three candidates through those criteria and the decision usually makes itself — and it is your decision, documented, rather than a vendor preference inherited by default.

Decide the architecture with us

An architecture session that fixes where card data will flow, what that means for your assessment scope, and which gateway capabilities your product actually needs.

Start the conversation