Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.augustus.com/llms.txt

Use this file to discover all available pages before exploring further.

When an Open Banking payment fails, Augustus includes status classifications in the order_updated webhook event to explain why. Use these to provide better user messaging and handle edge cases.

​
Status classifications

Augustus uses a two-level classification system to categorize payment failures. When an order_updated event is fired with a failed or canceled status, the payload includes a statusClassification object: 
{
  "statusClassification": {
    "primary": "payment_execution_failed",
    "secondary": "insufficient_funds"
  }
}
  • primary is the broad failure category (one of three values, listed below)
  • secondary is the specific reason within that category

​
Primary classifications

​
Payment authorization failed

The payment was rejected during the authorization phase, typically due to user action or bank restrictions. Common scenarios:
  • User rejected or cancelled the payment in their bank app
  • User input the wrong credentials with their bank
  • User’s account has restrictions preventing instant transfers
Handling recommendations:
  • Suggest trying again and checking their log in details carefully
  • Suggest retrying with a different bank
  • Suggest checking their bank account for restrictions

​
Payment execution failed

The payment was authorized but failed during execution, usually due to technical or account-related issues. Common scenarios:
  • Insufficient funds in the account
  • Account limits exceeded
  • International transfer was blocked by the bank
  • The payment was rejected by the bank
  • Bank system errors or maintenance
  • Payment not settled within the required timeframe
Handling recommendations:
  • For insufficient funds: Suggest checking account balance and retrying
  • For account restrictions: Recommend contacting the bank
  • For settlement failures: Retry the payment, if the original payment later arrives it will be returned

​
Payment abandoned

The payment process was started but never completed, often due to user inaction. Common scenarios:
  • User closed the browser/app during payment
  • User did not complete the payment in time and the session timed out
  • The user cancelled the payment with their bank side
Handling recommendations:
  • Provide clear messaging about incomplete payments
  • Inform users of the max time within which payments must be completed
  • Offer to restart the payment process

​
Secondary classifications

CodeDescription
wrong_credentialsUser entered incorrect bank credentials during authentication
incorrect_2fa_responseUser provided incorrect two-factor authentication response
pin_blockedUser’s PIN is blocked, e.g. after multiple failed attempts
no_active_tan_methods_availableNo active TAN (Transaction Authentication Number) methods available
timeoutThe payment request timed out due to slow response from bank systems
connection_to_bank_failedThe user’s bank is not responding to the payment request
bank_errorThe bank’s system returned an error during processing
bank_under_maintenanceThe user’s bank is currently under maintenance
insufficient_fundsThe user’s account has insufficient funds for the payment
account_limit_exceededThe payment exceeds the user’s account transfer limits
international_transfer_blockedInternational transfers are blocked for this account
international_transfer_limit_exceededThe payment exceeds international transfer limits
instant_transfers_not_enabledInstant transfers are not enabled for this account
user_blockedThe user’s account is blocked or restricted
unsupported_bank_accountThe bank account type is not supported for the requested transfer
payment_rejectedThe payment was explicitly rejected by the bank
cancelledThe payment was cancelled by the user or bank
payment_not_settledThe payment was not settled within the required timeframe
For the full status lifecycle, see Status Flow. For webhook setup and signature verification, see Webhooks.