Appendices

Appendix E — Failure Mode Catalogue

Payments fail in patterns. This catalogue lists the recurring ones by lifecycle stage: the symptom you see, the cause behind it, where to look first, and the chapter with the full story.

Authorization

SymptomLikely causeWhere to lookChapter
Decline with generic "do not honor"Issuer risk logic — catch-all refusalIssuer decline code detail from PSP, retry on another day/methodCh 9
Soft decline spikeInsufficient funds, velocity limits, issuer outageDecline-code mix by issuer/BINCh 9, 15
Hard declines recurringCard closed, reported stolen, expiredStop retrying; trigger credential refreshCh 15
Cross-border declines elevatedIssuer distrust of foreign acquiringLocal acquiring / local MID strategyCh 8, 32
3DS abandonmentChallenge friction, broken redirect on mobileFunnel between 3DS start and completionCh 11

Capture & Clearing

SymptomLikely causeWhere to lookChapter
Auth approved, capture failsAuth expired before captureDays between auth and capture vs scheme limitsCh 9
Captured amount ≠ authorized amountTips, partial shipments, currency driftAuth-capture mismatch rules for your MCCCh 9
Duplicate chargesWebhook/system retries without idempotency keysIdempotency handling in your integrationCh 9, 32
Partial capture unexpectedSplit shipments, partial approval logicOrder-to-capture mappingCh 9

Settlement & Payouts

SymptomLikely causeWhere to lookChapter
Payout smaller than salesFees netted from gross, refunds/chargebacks deductedSettlement report line itemsCh 4
Payout missing entirelyRolling reserve, risk hold, verification lapsePSP reserve terms and account statusCh 26
Settlement timing driftWeekends, holidays, cutoff windows, T+2 conventionsScheme calendar vs your accrual assumptionsCh 4

Reconciliation

SymptomLikely causeWhere to lookChapter
Books never match payoutsMatching at wrong granularity (batch vs transaction)Ledger design; transaction-level referencesCh 4, 18
FX differencesConversion at different times/rates than bookedSettlement currency vs presentment currencyCh 8
Unidentified incoming transfersCustomers pay without referencesVirtual accounts as reconciliation primitivesCh 18

Recurring & Stored Credentials

SymptomLikely causeWhere to lookChapter
MIT declines after months of successCard reissued; stored PAN staleNetwork tokens / account updater coverageCh 12, 16
Renewal failures clustered at month endPayday timing, expired cards batchRetry schedule vs calendarCh 15
"Unauthorized" recurring disputesWeak mandate evidence, unclear descriptorCIT/MIT flags, mandate records, billing descriptorCh 16
Direct debit returns weeks laterRevocation, closed accounts, disputes inside refund windowScheme return codes and windowsCh 20

Disputes

SymptomLikely causeWhere to lookChapter
Chargeback rate creeping upFriendly fraud, unclear descriptors, delivery disputesReason-code distributionCh 13
Losing winnable representmentsEvidence not matched to reason codeRepresentment package qualityCh 13
Network monitoring program letterDispute ratio breached scheme thresholdsChargeback ratio trend; remediation planCh 13, 26

Compliance & Off-boarding

SymptomLikely causeWhere to lookChapter
Sudden account termination by PSPRisk-appetite change, prohibited-category drift, MATCH listingYour MCC, dispute ratio, content of recent flagsCh 26
Funds frozen pending "review"AML alert, sanctions near-match, unusual velocityKYC file freshness; transaction pattern changesCh 26
Stablecoin funds stuckOff-ramp banking issues, blacklisted address upstreamIssuer/ramp status; address screeningCh 28, 30
QR/proxy payment to wrong recipientStale proxy mapping, static QR misuseProxy registry, dynamic QR adoptionCh 19
Using this catalogue — Most payment incidents are one of these patterns wearing a costume. Identify the lifecycle stage first, then the symptom row; the chapter reference gives you the mechanism, which is what you actually debug against.
The Money AtlasAppendix E — Failure Mode Catalogue