Mada
Mada is the national card scheme. Where an organisation accepts card payment, the contact it generates is about transactions that did not go as expected.
Mada is the national card scheme. Where an organisation accepts card payment, the contact it generates is about transactions that did not go as expected.
What Mada transaction data is, and where it sits
Mada is the domestic debit network used across the Kingdom, operated by Saudi Payments under SAMA, and the scheme behind the debit cards Saudi banks issue. For merchants and service providers, the questions it produces are transactional: did the payment succeed, why was it declined, where is my refund.
An assistant does not connect to Mada itself. The scheme carries payments between banks; the record a merchant can read sits with whoever processes its card payments — the payment gateway for online sales, the acquiring bank or terminal provider for payments in store. That record is what this connection reads.
None of these require a payments specialist to answer, and all of them currently do.
- Transaction status — approved, declined, pending.
- Decline reasons — the category of failure, at the level a merchant may disclose.
- Refunds — whether a refund has been issued and when it should appear.
- Settlement — when a transaction settles to the merchant.
- References — the identifiers that link a transaction to an order.
Mada payment questions Elbi can answer
Did my payment go through?
Transaction status, answered directly.
Why was I declined?
The category of decline, at the level a merchant is permitted to explain.
Where is my refund?
Refund status and expected timing, which is the most escalation-prone payment question.
When will it settle?
Settlement timing for merchants.
Was I charged twice?
Duplicate detection, which resolves a common and alarming query.
What is this transaction?
Matching a transaction to an order.
How Elbi reaches Mada transactions
- Through your processorThe connection is made to the gateway or acquirer that handles your card payments, using credentials from that provider. If online and in-store payments go through different providers, each is connected separately, and the assistant knows which one to ask.
- Online: by order referenceFor an online order, the assistant finds the payment by your order reference in the gateway's records. Those records show the payment was made with a Mada card, whether it was approved, and any refund recorded since.
- In store: carefullyA shopper who paid at a terminal usually has no account to sign in to. Rather than look up transactions for an unverified caller, the assistant explains what the receipt shows, sets out your refund rules and passes a disputed charge to staff with the receipt details.
- Co-badged cards explainedMany Mada cards also carry Visa or Mastercard, so a customer may not know which network a payment used. The processor's record shows which one it was, which settles a question customers genuinely ask.
- Declines at the right levelOnline Mada payments normally pass through the issuing bank's verification step, and an unfinished verification is a frequent reason a payment did not complete. The assistant names the category and the next step; the issuer's detailed reasons stay with the issuer.
- Refunds reported, not madeA refund goes back to the card it came from. The assistant reports when your side processed it and the period you publish for it to appear; issuing a refund stays with your staff.
Scope and control for Mada payments
| Source of the data | Your gateway, acquiring bank or terminal provider — never the scheme directly. What the assistant can see is limited to what those providers make available to you as the merchant. |
|---|---|
| Direction of access | Read-only. Status, amount, time, card brand and refund state are read; no payment, reversal or refund is created through the connection. |
| Card data and codes | The assistant never asks for a card number, CVV or the one-time code a bank sends. PCI DSS is why card numbers stay out of the chat; the one-time code is the customer's own and should never leave their phone. |
| Who can see what | Online customers see their own transactions after signing in. Staff see what their role in your organisation allows. In-store transactions are not disclosed to unverified callers. |
| Credentials | Issued by you from your processor's merchant account, kept for this connection and used only to query. You can rotate or revoke them at any time, on your side. |
| Retention | What is read is used to answer and is gone with the conversation: message content is destroyed within 24 hours, usually when the conversation ends. No external AI service sees it. |
| If a provider is down | The assistant says it cannot check that payment right now and offers a person, rather than guessing from an older answer. |
What this replaces
Refund status is the highest-value question here. Customers who have been refunded frequently cannot see it yet, contact repeatedly, and escalate — and the answer is a date that already exists.
Decline explanation is the second. There are limits on what a merchant may say about why a card was declined, and an assistant should stay firmly within them — but explaining the category and the next step resolves a large share of abandoned transactions.
Duplicate charge queries are the third. They are alarming to customers, common in practice, and usually resolved by looking at two records.
Where Mada questions come from
E-commerce
Payment and refund status at volume.
Retail
Transaction queries against in-store payment.
Services
Recurring payment failures and retries.
Any merchant
Refund timing, the most escalation-prone payment question.
Getting value from Mada payment records
Refund status earns its place first. A Mada refund leaves your side on a known date and then takes time to show on the customer's bank statement, and the customer sees only the second half. Telling them when it left you, and the period you publish, answers the question that otherwise comes back again and again.
The apparent double charge is next. Sometimes it is a genuine duplicate; more often one of the two lines is an attempt that failed, which the bank may still show as pending for a while. Reading both records and saying which one completed resolves a worrying message quickly, and a real duplicate goes straight to staff with the evidence attached.
Before-purchase questions round it out: whether you take Mada online, whether it works with Apple Pay on your site, whether they can tap to pay at your tills. None of these needs a lookup, only an accurate description of what you accept.
What connecting Mada payments involves
- Find where Mada records liveList every provider that processes your card payments — the online gateway, the acquiring bank, the terminal provider — and what each lets a merchant retrieve. Some offer an API; some only reports.
- Choose the channels to coverOnline payments are the natural start, because the customer is already signed in and the order reference is known. In-store coverage can follow if your provider's records support it.
- Issue processor credentialsFrom each provider's merchant account, your team creates credentials for this connection only. They stay under your control and can be revoked there.
- Align referencesMake sure the order or receipt reference a customer can see is the same one stored with the transaction. Without that link, matching a question to a payment is guesswork.
- Agree decline and refund wordingYour payments lead signs off the categories a customer will hear and the refund period you publish, so the assistant repeats your policy rather than inventing one.
- Test with real edge casesA verification abandoned halfway, a co-badged card, a partial refund, two attempts a minute apart. Each is checked before launch.
Governing debit-card records
A Mada transaction is a debit from someone's bank account at a named merchant, at a known time. Under the Saudi Personal Data Protection Law that is personal data, and it reveals more than most records: where a person shops, and when. The assistant should read only the transaction being asked about, and only once the person asking is shown to be its owner.
The second governance point is fraud. A familiar scam impersonates a bank or a merchant and asks for a card number or the code the bank has just sent. An assistant that states plainly, every time it is asked, that it will never request either gives customers a simple rule to hold on to.
How merchants handle Mada questions today
Online, the usual route is a support agent searching the gateway's merchant dashboard; in store, a manager checking the terminal's transaction list or the acquiring bank's portal. Both are reliable, both depend on who is on shift, and in-store checks in particular tend to wait for the next working day.
Clear receipts, a checkout that says plainly when a payment has not gone through, and a published refund period prevent a good share of questions. Where a customer's question is really about their bank — a hold on the account, a limit, a card that has been blocked — the right answer from anyone at the merchant, person or assistant, is to direct them to their bank.
The mistake to avoid is describing the connection as "integrating with Mada". It sets the wrong expectation with your own security and finance teams; the conversation that gets approved is the one about which processor's records are read, and how.
What merchants see with Mada payment status connected
Common questions
At the category level a merchant is permitted to disclose, with the next step. Detailed issuer reasons are not the merchant's to share.
No. It reports refund status. Issuing one is a financial decision with a person.
Where transaction records are connected, yes — a common and alarming query resolved by comparing two records.
No. Merchants do not get a direct connection to the scheme. The assistant reads Mada transactions from the gateway or acquirer that processes your payments, using credentials you issue there and can revoke.
Where your acquiring bank or terminal provider makes those records available, yes, for staff and for identified customers. Otherwise the assistant explains receipts and refund rules and hands specific transactions to staff.
Never. It does not ask for a card number, CVV or one-time code, and says so when asked. A message requesting them in a merchant's name should be treated as a scam.
Connect Mada payment status to Elbi
Mada transaction and refund status, read from your own gateway or acquirer, answered in Arabic and English.