Payment Processing Format, Timeout & System Errors: Code 30, 06, 68, 96 + Fixes

Use this guide to troubleshoot processing-layer failures (format errors, timeouts, routing and switch issues) without creating duplicates or double charges.

More banking guides Banking hub Banking code directory

TL;DR

✓ First determine if the error is local (integration) or systemic (processor/network).
✓ Use idempotency/duplicate controls for retries.
✓ Format errors usually require fixing request fields—not retrying.
✓ Time-based errors require reconciliation before resubmission.

Quick Navigation

Symptoms Root Causes Step-by-step fixes What NOT to do If it persists Code directory Related guides & hubs FAQ References

Symptoms / When you see this

✓ Code 30/06/96-like processing errors.
✓ Timeouts where final state is unclear.
✓ Duplicate detection errors after retries.

Root causes (grouped)

✓ Integration/format problems in request payloads.
✓ Processor routing/switch outages or congestion.
✓ Timeout windows exceeded with unknown final state.
✓ Duplicate submission due to retry logic without idempotency.

Step-by-step fixes (safe, prioritized)

✓ Check whether failures spike across merchants/cards (systemic) vs one integration (local).
✓ For format errors, fix request mapping (field lengths, required fields, transaction type).
✓ For timeouts, reconcile transaction status before retrying to avoid duplicates.
✓ Use idempotency keys or gateway duplicate protection for any retry path.
✓ Escalate to processor with request/response IDs and timestamps for systemic incidents.

What NOT to do

✓ Do not resend blindly after timeouts.
✓ Do not “fix” format errors by random retries; correct the payload instead.
✓ Do not disable security controls to test and forget to revert.

If it persists (escalation checklist)

✓ Collect: gateway request IDs, raw response fields, timestamps, and affected card/network info (non-sensitive).
✓ Include correlation IDs from your API logs for fast support triage.

Code directory within this guide

✓ Processing errors are often context-driven. Use logs and reconciliation tools, not repeated retries.

Code	Meaning	Next step
30	Format error — Response code 30 indicates the authorization message failed formatting or validation checks.	Follow the checklist on the code page
96	System malfunction — This code indicates the transaction failed due to a system malfunction in the processing chain.	Follow the checklist on the code page
ERR-AUTH	Authorization failed — This code indicates the system could not authorize the requested action under current security, account, or policy rules.	Follow the checklist on the code page
ERR-LIMIT	Limit exceeded — This code indicates the request exceeded a configured limit for amount, frequency, or permitted transaction activity.	Follow the checklist on the code page
ERR-REVERSAL	Reversal required — This code indicates the system flagged the transaction for reversal handling due to an incomplete, conflicted, or failed processing outcome.	Follow the checklist on the code page
ERR-TIMEOUT	Session timeout — This code indicates the session expired or timed out before the transaction could be completed.	Retry once; validate connectivity and service status
ERR-TXN-FAILED	Transaction failed — This code indicates the transaction could not be completed and was marked as failed by the bank or payment system.	Follow the checklist on the code page
Payment reversed	Payment canceled/undone — This status indicates the system reversed the payment, undoing the original transaction outcome through a corrective or cancellation process.	Follow the checklist on the code page
R03	No account/unable to locate — This code indicates the RDFI could not locate an account matching the information provided.	Follow the checklist on the code page
R14	Invalid individual ID — This code indicates the individual identification information in the ACH entry was deemed invalid by the receiving institution’s processing rules.	Follow the checklist on the code page
Z5	Manual review — This code indicates the item requires human review before the system will allow completion or final posting.	Follow the checklist on the code page
Z9	Risk assessment — This code indicates the transaction is undergoing risk assessment before the system decides whether it can proceed.	Follow the checklist on the code page

Tip: If your exact code isn’t listed, use the closest hub link above and browse related prefixes or message patterns.

FAQ

Why is code 30 different from code 05?

30 is typically a message/format problem; 05 is an issuer decision category.

Should I retry after a timeout?

Only after reconciling status and using duplicate protection to avoid double charges.

How do I know it’s systemic?

If many cards or merchants fail simultaneously with similar system/routing codes, it’s likely systemic.

What fixes format errors fastest?

Field-level validation and alignment to the processor API requirements.

What if I see duplicates?

Stop retries and reconcile. Implement idempotency so resubmits don’t create new charges.

Do processors expose detailed reasons?

Sometimes via logs or extended fields. Support often needs correlation IDs.

Can I prevent many of these errors?

Yes—validate payloads, handle retries carefully, and monitor processor health.

What should I send to support?

Timestamps, request/response IDs, and reproducible steps with minimal sensitive data.

References / Notes

✓ Gateway reconciliation logs
✓ Processor incident support channels
✓ Integration documentation