In our exploration of the 4-Party Model, we solved the first half of the coffee shop mystery. We explained how a small credit union in Ohio could instantly evaluate your $5 purchase in Tokyo, approve it, and guarantee the funds.
But we left a massive gap on the other side of the transaction.
Before the Ohio credit union can approve anything, the coffee shop’s point-of-sale (POS) terminal must send a request to Visa. But to talk to Visa, that little terminal on the counter needs to speak a highly complex, rigidly formatted, encrypted protocol called ISO 8583—a messaging standard developed in the late 1970s.
The barista doesn’t know how to code this. The coffee shop owner doesn’t have a direct contract with Visa. And they certainly don’t have a dedicated fiber-optic line plugged into Visa’s data centers.
So, how does a $5 authorization request make it out of that Tokyo coffee shop, get translated into 1970s network code, and find its way to Ohio?
The answer lies in the merchant’s side of the network: a split architecture of risk and software known as the Acquiring Stack.
1. The Core Illusion: The Abstraction Layers
When you click “Buy Now” on a website or tap your phone at a register, it feels like a direct connection to your bank. It isn’t.
There is a chain of middlemen abstracting the complexity away from the merchant. The actual path of the data looks like this:
The Coffee Shop’s Terminal ➡️ Payment Gateway ➡️ Acquiring Bank ➡️ Visa/Mastercard Network ➡️ Issuing Bank (Ohio)The merchant never talks to the network. The network never talks to the merchant. They rely on distinct entities to bridge the gap: the Acquiring Bank and the Payment Processor.
2. The Two Halves of the Acquiring Stack
To understand how the merchant gets paid, you have to separate the acquiring stack into its two fundamental components: the Risk Taker and the Software Layer.
2.1. The Acquiring Bank (The Risk Taker)
Visa and Mastercard do not accept transactions directly from merchants. They only accept transactions from licensed financial institutions.
Therefore, the coffee shop needs a sponsor. They need a licensed bank to agree to take their transactions, bundle them up, and present them to the Visa network. This is the Acquiring Bank.
The Acquirer’s primary role is not software; it is underwriting and risk.
When the coffee shop signs up to accept cards, the Acquirer evaluates them. What if the coffee shop is a fraud? What if they process $50,000 in fake transactions today, pay out the cash to themselves, and disappear tomorrow?
Because the Issuer (Ohio Credit Union) is agreeing to honor the authorization for the consumer, someone must guarantee the $5 to the Issuer if the merchant turns out to be a scam. That someone is the Acquirer. The Acquiring bank takes on the default risk of the merchant. If the merchant commits fraud, the Acquirer has to eat the cost.
2.2. The Payment Processor / Gateway (The Software Layer)
Because acquiring banks have historically focused on regulation, underwriting, and risk management rather than merchant-facing software, specialized payment technology companies emerged to build faster, more developer-friendly interfaces.
This is where the software layer enters the picture. Modern companies like Stripe, Adyen, and Square combine gateway, processing, and merchant services into a single platform, often working with or operating alongside an underlying acquiring bank.
Whether it’s a website sending a simple REST API call (like POST /charge) or a physical terminal speaking a specialized point-of-sale protocol, the processor exposes a simple interface to capture the payment data. The processor then receives this clean data and performs a massive amount of work in milliseconds:
- Routing: It looks at the card number (the BIN) to figure out if it should route to Visa, Mastercard, or a local Japanese network.
- Translation: It wraps that simple API call or terminal protocol into the monstrous, highly specific ISO 8583 message format that the Visa network demands.
- Security: It handles the encryption keys and tokenization so the coffee shop never actually touches your raw credit card number.
The Processor hands this perfectly formatted, encrypted message to the Acquiring Bank, who then submits it to the Visa network.
(Note: While companies like Stripe create a seamless “one-stop-shop” for the merchant, architecturally, the risk of the acquirer and the software of the processor remain distinct functions).
3. The Reversed Flow: Funding the Merchant
We know how the $5 is authorized. We know from the 4-Party Model that at the end of the day, Visa uses Netting to settle the bulk difference between all Issuers and all Acquirers.
But how does the coffee shop actually get their money?
Visa coordinates settlement between issuers and acquirers through designated settlement banks. Once this settlement occurs, the Acquirer has the funds. But the Acquirer represents 10,000 different coffee shops, clothing boutiques, and hardware stores.
The Acquirer does exactly what Visa does: it calculates each merchant’s net settlement amount.
They look at all the approved transactions for your specific coffee shop in Tokyo that day. Let’s say you bought a $5 coffee, and 400 other people did too. The Acquirer calculates the total: $2,000.
Then, in a beautifully ironic twist, the final leg of this high-speed, global, instant-authorization network relies on the slowest rail in domestic finance.
The Acquirer initiates a batch domestic transfer (like a Zengin transfer in Japan) to push that $2,000 to the coffee shop’s actual local bank account. Because of this batch processing, even though the authorization happened in two seconds, the coffee shop doesn’t actually see the cash in their bank account until the next business day (T+1) or the day after (T+2).
4. The Economics of Acquiring: Razor-Thin Margins
Everyone knows that when you pay with a card, the merchant pays a fee—typically around 2.5% of the transaction, known as the Merchant Discount Rate (MDR).
But where does that 2.5% actually go? It is not a black box. The Merchant Discount Rate is typically divided among three main buckets:
- Interchange Fee: This goes directly to the Issuer (the Ohio Credit Union) to fund your rewards and cover their fraud risk.
- Network Assessment Fee: This goes to Visa for maintaining the global routing infrastructure.
- Acquirer/Processor Fee: This is what the Acquirer and the Gateway get to keep.
The exact distribution of this rate changes enormously depending on the country, whether it’s a debit or credit card, the type of rewards card, if it was card-present or online, and the size of the merchant. However, the Acquiring side of the business almost always operates on razor-thin margins. They are handling massive throughput, taking on the default risk of the merchant, building highly available software, and navigating complex compliance—but they only get to keep a small fraction of the total fee.
Because the payment processing margin is so brutally thin, Acquirers and Processors cannot survive on volume alone. This is the exact economic reason why companies like Square and Stripe have expanded far beyond just “accepting cards.” They have to upsell the merchant. They sell POS hardware, business loans, payroll software, and fraud protection tools.
The gateway is no longer just a door to the network; it is a loss-leader to sell software to the coffee shop.
5. The Illusion Revealed
The next time you tap your card at a small shop, look at the terminal. In that brief second before the screen says “Approved,” a staggering amount of architecture has been executed.
A software gateway translated a modern web request or terminal signal into a 1970s financial protocol. A licensed bank sponsored that transaction, accepting financial responsibility for the merchant under the card network’s rules. The message bounced across oceans to your issuer, and back again.
And yet, the only thing the barista sees is a green checkmark, completely unaware of the vast, multi-layered scaffolding required to turn their coffee into cash.