
A card payment is approved in about a second, settled a day or two later, and can be disputed for months. The card networks set many of the rules, and card data must be protected at every step. This is how I take a card change from idea to live, safely, for banks that issue cards and for those that help shops accept them.
New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.
How a card payment moves
Read from left to right. Steps 1 to 4 are the approval, which takes about a second. Step 5, when the money really moves, comes later, usually in 1 to 2 days. The band at the bottom shows the protections at every step, from the tap at the till to a dispute months later.
Cards in one minute
Cards are the most used way to pay in the US. In 2024 there were 120.6 billion debit card payments and 67.1 billion credit card payments. Cards made up 79% of noncash payments by number, but only about 8% by value (Federal Reserve Payments Study, July 2026).
| Step | What happens | When |
|---|---|---|
| Authorization | The cardholder’s bank (the issuer) says yes or no, through Visa, Mastercard or another network | About a second |
| Clearing | The shop’s bank (the acquirer) sends the final purchase details | Same or next day |
| Settlement | Money moves from issuer (the bank that gave you the card) to the shop’s bank, minus fees | Usually 1 to 2 days |
| Dispute | The cardholder can dispute; their bank can take the money back from the shop (a chargeback) | Weeks to months |
Three things that make cards different
- The networks write many of the rules. Visa and Mastercard change them in regular releases, with fixed dates you can’t move. List those dates first and plan backwards.
- Card data is protected by PCI DSS (now v4.0.1) wherever it is stored, processed or sent. Replace card numbers with tokens, keep real card numbers out of logs and test data, and keep as few systems as possible near card data.
- The money moves after the approval. A change isn’t really tested until clearing, settlement, fees and disputes all match up.
| Type | Money comes from | Main consumer rule |
|---|---|---|
| Debit | The customer’s bank account | Regulation E (plus Regulation II, which caps the fee big banks earn on debit cards, called interchange) |
| Credit | A credit line repaid later | Regulation Z (the US rule for credit) |
| Prepaid | Money loaded in advance | Regulation E (the US rule that protects consumers’ electronic payments), including the Prepaid Rule |
Building it: short cycles, firm checkpoints
Most card teams freeze changes over the holiday shopping season, often from mid-November to early January. Plan your releases around it. The gates that matter:
| Gate | Done when |
|---|---|
| E2E exit | Network and processor tests passed, 95% or more of our tests passed, approvals fast enough at the busiest time, the money matches, no real card numbers in logs |
| UAT exit | Business, disputes and fraud scenarios signed by the people who use them |
| Go-live | Card-data security in place, pilot cards checked, fraud checks and the extra online check (3-D Secure) live, backup approvals (stand-in) tested |
Prove it with real cards. Run a “friends and family” pilot. Employees tap, insert and shop online, add the card to a wallet, make a refund and raise a dispute. Match every transaction before you widen the rollout.
Running it live
Watch the approval rate above everything. A sudden drop is the first sign of trouble, from an outage to a fraud rule that blocks good customers. Keep stand-in processing ready, so the network approves small purchases if your system is down. Alert on declines, slow responses and missing files, and run card operations and the fraud desk around the clock.
Download the full runbook (PDF, 13 pages)
Every phase in detail for issuing and acquiring, with rules, PCI DSS, network certification, exit criteria and sign-off, a real-card pilot plan, controls, alerts, incident runbooks, disaster recovery and audit checklists.
The files behind this runbook
Every part of this runbook touches the same handful of files. Here is where each one shows up. For what is inside each file, with samples and a step-by-step checklist, see Card payments, step by step.
| File or moment | Where it matters in this runbook |
|---|---|
| ISO 8583 0100 / 0110 | How a card payment moves |
| 0400 reversals | Three things that make cards different |
| Clearing files and settlement | Cards in one minute |
| Refunds and chargebacks | Running it live |
More payment runbooks
- ACH payments
- Wire payments (Fedwire and CHIPS)
- Instant payments (RTP and FedNow)
- Checks and remote deposit capture
- Cross-border payments over SWIFT
- Zelle for banks
- PayPal integration
- Embedded payments
The bottom line
Card delivery works when you respect three things: the network calendar, the card data, and the money that moves after the approval. Watch the approval rate every day, and you will see problems before customers tell you.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help