Field Guide
Card issuing: launching a card program
09
Common mistakes
1 min read · Chapter 9 of 10
What usually goes wrong
| Symptom | Likely cause | First thing to check |
|---|---|---|
| Launch date slips by months | Bank due diligence, network approval or custom plastic running in sequence | Whether stock or virtual cards could ship while the rest finishes |
| Bank goes quiet after the early meetings | The program is outside its risk appetite, or the bank is under an order | Its public orders, and its list of prohibited programs |
| Ledger and the pooled account disagree | Timing items, unmatched clearings, refunds not linked to a purchase, fees netted | The daily tie-out, and who owns each break |
| Revenue drops by half in July | The bank crossed $10 billion at the prior year-end | The bank's year-end assets and your contract's termination rights |
| Interchange below plan | Low spend per card, or online debit routed to a cheaper network | Spend per active card and the network mix |
| Cardholders can't add the card to Apple Pay | Wallet approval incomplete, or push provisioning not entitled in a production app | The entitlement and the provisioning approval rate |
| Stored cards fail at merchants after a migration | The card number changed and tokens or account updates didn't follow | Token lifecycle updates for the new range |
| Funds frozen at a solvent bank | The bank can't verify who owns what in the pooled account | Whether the bank holds or can reach per-owner records |
| Credit partner losses land on the bank | The partner's guarantee or collateral fell short | Collateral terms and how fast the bank can draw them |