When a customer clicks “pay” on a well-built online store, roughly a dozen systems fire in under two seconds: tokenization, fraud scoring, authorization, routing, ledger entries, webhook notifications. The merchant sees a single confirmed order. Understanding what actually sits underneath that click has become essential knowledge for anyone building or scaling an online business, because the payment stack quietly determines conversion rates, cash flow, and how far a platform can expand.
The gateway layer: getting money in
The gateway is the front door. It captures card details or alternative payment credentials, tokenizes them so raw data never touches the merchant’s servers, and forwards the transaction for authorization. Modern gateways do considerably more than pass messages along. They handle strong customer authentication where regulation demands it, retry soft declines through alternative routes, and localize the checkout — presenting the payment methods a given market actually uses, since card-centric checkouts underperform badly in regions where bank transfers or local wallets dominate.
Routing is the underappreciated part of this layer. A sophisticated stack can send a transaction through different acquiring banks depending on card type, geography, or historical approval rates. A one-percentage-point improvement in authorization rates flows straight to revenue, which is why larger platforms obsess over routing logic that smaller merchants never see.
The wallet layer: where money lives between events
Between the moment funds are captured and the moment they are paid out, they need somewhere to exist — with an owner, a currency, and a running balance. This is the wallet and ledger layer, and it is the true heart of platform payments. Every user or seller gets a ledgered account inside a regulated environment; every movement of value is a double-entry record that can be audited, reversed, or split.
This layer is what enables the flows that simple shops never need: holding funds pending delivery, splitting one payment among several recipients, applying commissions automatically, managing balances in multiple currencies. The architectural requirements differ sharply depending on whether a business sells its own inventory or intermediates between third parties — a distinction with real legal weight, unpacked at blog.mangopay.com/en/home/what-is-the-difference-between-e-commerce-and-marketplaces. Choosing the wrong model early is one of the more expensive mistakes a platform can make, because retrofitting a ledger under a live business is open-heart surgery.
The payout layer: getting money out
Payouts are where infrastructure quality becomes visible. Sellers, creators, and partners want their money quickly, in their own currency, on their preferred rails. That means integrating with domestic banking networks across many countries, handling instant payout schemes where they exist, batching where they do not, and managing the failure modes: bounced transfers, closed accounts, mismatched beneficiary names. Each failed payout is a support ticket and a dent in trust, so mature stacks build automatic retry and reconciliation logic rather than leaving it to operations teams.
The layer nobody sees: compliance and risk
Woven through every layer is a mesh of obligations: verifying the identity of everyone who receives funds, screening against sanctions lists, monitoring transactions for laundering patterns, safeguarding customer funds in segregated accounts. This is the primary reason most platforms build on licensed infrastructure providers — firms such as mangopay.com operate under regulatory frameworks that would take a platform years and significant capital to obtain independently.
Buy the plumbing, build the product
- Gateways determine how much revenue you capture at checkout.
- Wallets and ledgers determine what business models you can support.
- Payout rails determine whether your sellers stay.
- Compliance determines whether you operate at all.
None of these layers is a differentiator customers will praise, but every one of them can quietly cap growth. The pragmatic pattern that has emerged is clear: platforms concentrate their engineering on the experience that makes them unique, and stand on infrastructure for the layers where correctness, licensing, and bank connectivity matter more than originality.
