compliance_resp_cd when a bill fetch, validation, or payment request fails. The accompanying compliance_reason gives the human-readable failure reason. Use these codes to identify the cause of a failure and to decide whether you can retry the request.
Retry categories
Each error code maps to a retry category that tells you how to handle the failure. The following categories apply across all error groups:NON_RETRIABLE: the request will fail again with the same input. Do not retry the same request. Correct the customer details or inform the customer, as indicated by the reason.RETRIABLE: the failure is temporary, usually a biller or network issue. Retry the request after a short delay.CONDITIONAL: the outcome depends on inner error codes returned by the biller or the switch. Inspect the accompanying reason before you decide whether to retry.
Some reasons include additional timing guidance, such as retrying later or on the next day. Always honour the timing hint in the reason before you retry.
Bill fetch error codes
The Bill Fetch Response API returns these codes when a fetch request fails. Fetch codes use theBFR prefix.
Bill validation error codes
The Bill Fetch Response API returns these codes when a bill validation request fails. Validation codes use theBVR prefix.
Payment posting error codes
The Bill Payment Response API returns these codes when a payment fails at the biller. Payment codes use theBPR prefix.
Infrastructure error codes
These codes indicate a transport or switch-level failure between the operating units, rather than a biller decision. Codes with theBOU prefix relate to the Biller Operating Unit, and codes with the COU prefix relate to the Customer Operating Unit.