01.02 · Concept · Free
Who Says No, and Why
Place the merchant, gateway, processor, acquirer, network and issuer in order, and say which one actually decides whether a payment is approved.
Curated for this lesson1/2
How Money Actually Moves
MasterCard Payment Facilitator Module 1
Mastercard’s payment-facilitator module is likely to define ecosystem roles around merchant, acquirer, network, and issuer.
The issuer normally makes the approval decision in a card payment. The request usually moves from merchant to gateway to processor and acquirer, then through the card network to the issuer. Other parties may format, route, validate, or block messages, but the issuer is usually where the real authorisation yes or no originates.
What this lesson answers
- who approves a card payment transaction
- card payment flow merchant gateway processor acquirer issuer
- why did a card payment get declined
Notes
A card payment is not just “the merchant asks the bank.” The usual online path is merchant, gateway, processor, acquirer, network, issuer, then the answer returns back along a similar path. The merchant starts the sale. The gateway securely captures and formats the payment request. The processor and acquirer help the merchant’s side connect to the card system. The card network routes the request. The issuer is the cardholder’s bank or card provider.
The key mental model is a relay, not a committee. Each party forwards, translates, checks, or routes the authorization message, but the issuer is the party that normally says yes or no. The issuer decides whether the card is valid, whether the account is in good standing, whether funds or credit are available, and whether the transaction looks risky. The approval code or decline response then travels back to the merchant.
A common misconception is that Visa, Mastercard, the gateway, or the merchant “approves” the payment. They usually do not. The network can route and enforce rules, the gateway or processor can reject malformed or obviously invalid requests, and the merchant can choose not to accept a transaction, but the core authorization decision for a normal card payment belongs to the issuer.
After this lesson, you should be able to read a payment diagram and put the actors in order: merchant to gateway to processor/acquirer to network to issuer. You should also be able to explain a decline without guessing: the visible merchant system may show the decline, but the real “no” usually originated from the issuer or from a pre-issuer technical or fraud check along the path.
References
Common questions
- Does Visa or Mastercard approve card payments?
- Usually no. The card network routes the authorisation request between the merchant side and the issuer, and applies network rules. For a normal card payment, the issuer decides whether to approve or decline based on the card, account status, available funds or credit, and risk signals.
- Where does the gateway fit in a card payment?
- The gateway sits near the merchant side. It captures the payment details, secures them, and turns the sale into a properly formatted request for downstream payment systems. It can reject bad or incomplete requests, but it is not normally the party making the core issuer authorisation decision.
- Can a payment be declined before it reaches the issuer?
- Yes. A malformed request, failed validation, merchant rule, processor check, or fraud control can stop a transaction before issuer authorisation. That is different from an issuer decline. In practice, the merchant system may show the same broad failure to the user, even though the source of the no is different.
Short definition: what is Who Says No, and Why?