Directory · Interchange Optimization
Interchange Downgrade Reasons, and Which Ones You Can Fix
Published September 30, 2026 · Last reviewed · B2B Pay Hub editorial team · Reviewed by a B2B Pay Hub payments specialist
What each common downgrade means, why it happened, and whether it is fixable on your side or your processor's. Most are fixable, and most businesses never see them because tiered pricing hides them.
What a downgrade actually is
A downgrade occurs when a transaction fails to meet the requirements of the interchange category it would otherwise qualify for, and settles at a more expensive one instead. It is not an error and produces no alert — the payment succeeds normally and simply costs more. On tiered pricing a downgrade is invisible because it is absorbed into a qualification bucket, which is the single strongest practical argument for interchange-plus.
Common downgrade causes in B2B
| Cause | What happened | Fixable by |
|---|---|---|
| Missing Level 3 line-item data | Transaction carried no per-item detail | You — usually an ERP connector rather than a virtual terminal |
| Missing sales tax or exempt flag | Tax field empty rather than flagged exempt | You — order entry configuration |
| Missing customer or PO reference | Level 2 requirement not populated | You — make the field required at order entry |
| Freight billed separately | Required freight field absent from the transaction | You — bill freight on the same invoice |
| Late settlement | Batch not settled within the required window | You — batch timing, often just a schedule change |
| Address verification not performed | AVS required for the category and not run | You or your gateway configuration |
| Consumer card presented | No Level 3 category exists for consumer cards | Nobody — this is correct behaviour, not a fault |
| Processor does not pass Level 3 | Data sent but not transmitted onward | Your processor — ask them directly |
Educational reference material, not legal, tax or compliance advice. Rules, banking availability and provider policies change; check the linked primary source and the last-reviewed date before relying on anything here.