A tiny journey through modern payments

What happens in the 2 seconds after you tap Pay?

A checkout feels instant. Behind that tap, a short chain of systems asks a big question: can this payment be approved?

A quick field guide · Payments, explained

If you have two minutes

  1. Your phone sends payment credentials securely; the shop does not simply receive your card number.
  2. The request travels through payment systems to the bank that issued your card.
  3. An approval comes back quickly — but approval is not the same as final settlement.

Follow the payment

00.0 / 2.0 sec

Press play to send the authorisation request out — then watch the answer return.

Phone & walletTap + authenticate
Shop checkoutCreates the request
Payment providerSecures and routes it
AcquirerMerchant's bank side
Card networkFinds the issuer
Issuing bankChecks and decides
Request travelling to the bank →
00.0s · START

One tap starts the chain

Your wallet or card app confirms the payment method and may ask for biometric or device authentication.

About 2 seconds · illustrative timing

Then the answer comes back

The issuer checks things such as available funds or credit, card status, security signals and risk rules. It sends an approve or decline response back through the network and payment chain. The checkout can then show confirmation or ask you to try another method.

✓ Approved

The merchant gets an authorisation — a promise to honour the amount, subject to the payment process.

↗ Settled later

Clearing and settlement move the funds between financial institutions later. That is a separate step from the quick approval.

Why it can feel instantaneous

These systems are built to exchange compact messages quickly and run in parallel with security checks. The exact route and timing vary by payment method, country, merchant setup and whether extra authentication is needed. The two-second journey is a useful illustration, not a service-level guarantee.