Field Guide
B2B payments: real-time payments and open banking
09
Common mistakes
1 min read · Chapter 9 of 10
What usually goes wrong
| Symptom | Likely cause | First thing to check |
|---|---|---|
| A request for payment never reaches the buyer | The buyer's bank isn't on the network or doesn't take requests | Reach for that bank, and whether the fallback fired |
| A payment is rejected and nothing settles | Funds or prefunding short, a limit, a negative-list hit, the clock | The rejection code; retry with a new message ID |
| Settled, but the supplier can't use it | The receiving bank is holding it for review | Whether the bank released it; keep the invoice open |
| Paid twice or the wrong amount | An AP error | A request for return; a credit memo meanwhile |
| Paid to a fraudster after a "new bank details" email | Business email fraud | Whether a name check and callback ran; call the bank at once |
| Cash arrives but can't be matched | Remittance dropped, or a new paying account | The end-to-end ID, and each customer's known accounts |
| A bank data feed goes dead | Consent expired or was revoked | Expiry warnings and the re-link flow |
| A tokenized account number stops working | The consent behind it lapsed | Don't store it as a permanent ID |