Skip to main content
You’ll hit these on payment-method discovery, UOB Rewards loyalty redemption and balance calls, and any operation a terminal can’t currently route or a token can’t support. Match the whole problem+json type URN — never a prefix or the text after the last : — and never title. See Problem format and retries for the response shape, the full HTTP status guide, and retry rules; the Retry? column below is that same per-status rule applied to each error.

Loyalty (UOB Rewards)

See Handle UOB Rewards void and refund restrictions, Handle UOB Rewards redemption failures, and Balance inquiry for where these surface.

Payment method selection

selected_payment_method on purchase and authorize — see Charge or authorize a payment.

Discovery

GET /v1/payment-methods and GET /v1/payment-brands — see Show payment methods at checkout.

Routing and capability

These occur when no acquirer terminal can currently handle the operation you requested — distinct from a card decline, which always requires a live terminal to have been reached. See Fix operations unavailable for your outlet for the full walkthrough.

Tokens

See Elements: expired sessions and tokens.

Next steps

Problem format and retries

The problem+json shape, HTTP status guide, and retry rules.

Payment operation errors

Auth, validation, idempotency, transaction-state, and reversal errors.

Decline codes

How a declined payment appears — that’s not an error.

Handle failures

Find the right recovery page by symptom.
Last modified on October 25, 2026