Understand error codes returned with a failed payment

Some failed payments come back with a numeric error code. Find the code below, and the action that goes with it.

The transaction is not in the right state

Code	What it means	What to do
`143`	Transaction not found, or its status does not allow this operation	Check the transaction ID, then read its current status with `GET /transactions/{id}`
`285`	Invalid transaction status	The transaction is already in a final state. Create a new payment session instead of retrying the same one
`261`, `263`	Payment not found or already processed	Do not resubmit. Check the status first, a second attempt may already have completed

The card or the amount is the problem

Code	What it means	What to do
`212`	Card data in the wrong format	Ask the buyer to re-enter the card
`219`	Card not found, the `cardId` is wrong or does not exist	Check the saved card ID
`121`	Card deactivated after a failed registration	Register the card again
`361`	Card not registered, the buyer chose not to save it	Ask for a new registration if you need a saved card
`151`	Amount not allowed: below €0.50 for a card payment, above the refundable amount, or outside your contract limits	Check the amount, then contact support if it looks correct
`209`	Suspected fraud	Ask the buyer to try another card or contact their bank
`304`	Transaction refused	Ask the buyer to try another card

Something went wrong on the processing side

Code	What it means	What to do
`124`, `170`, `171`, `172`, `190`	Error returned by the payment processor	Retry once with a new payment session, then contact support
`296`, `297`, `288`	Processor error, timeout or network error	Wait a few minutes and retry. Check the status page
`191`	Error while executing the operation (generic)	Contact support with the transaction ID
`138`	Feature not available under your contract	Contact support
If your code is not listed, contact support with the transaction ID. We map new codes as they appear.

Updated on: 01/10/2026