Transaction Error Codes

Various errors can occur during transaction processing. To clearly indicate where a failure occurred and who is responsible for resolving it, a structured set of error codes is used. These codes are included in the status detail of any failed transaction.

A separate consumer message is available for display to end users. This message can be localized and is designed to avoid exposing internal error codes or sensitive system details.

Validation

Validation errors, identified by codes starting with “V”, indicate an issue with the submitted data or the state of related entities such as the merchant account, store, or existing transactions. These errors can typically be resolved by correcting the input data or ensuring that all related entities are in the required state.

Code	Explanation	Consumer Message
VS01	No active subscription	A configuration error occurred
VS02	No active subscription in required currency	A configuration error occurred
VS03	Invalid action on service	A configuration error occurred
VS04	Invalid service	A configuration error occurred
VS05	Could not find terminal	A configuration error occurred
VS06	No active profiles in terminal	A configuration error occurred
VP01	Missing required payment method options	A configuration error occurred
VP02	Invalid payment method options	A configuration error occurred
VP03	Sum of order lines does not match sale amount	A configuration error occurred
VP04	No valid credentials	A configuration error occurred
VP05	Giftcard limit has been reached	Giftcard limit has been reached
VP99	General validation error	A configuration error occurred
VM01	Invalid mandate	Mandate is invalid
VR01	Original transaction is not successful	The transaction could not be processed
VR02	Refund limit for transaction has been reached	The transaction could not be processed
VA01	Authorization is not successful	Authorization failed
VA02	Capture amount exceeds available authorization amount	The transaction could not be processed
VI01	Merchant not found	A configuration error occurred
VI02	Merchant inactive	A configuration error occurred
VI03	Store not found	A configuration error occurred
VI04	Store inactive	A configuration error occurred

Processor

For processor errors (starting with P) the payment processor returned an error code indicating the transaction could not be completed. This could be caused by for example outages at the processor or because of the consumer not correctly completing the transaction.

Sometimes the processor can also return a status detail code, when present this can also be found on the transaction in the status processor code.

Code	Explanation	Consumer Message
PC01	3DS authentication failed	3DS authentication failed
PC02	3DS authentication was rejected by issuer	3DS authentication failed
PC03	3DS challenge not completed	3DS authentication failed
PC04	3DS exemption declined	3DS authentication failed
PC05	Insufficient funds	Insufficient funds
PC06	Card number invalid	Invalid card number
PC07	Pin invalid	Invalid pin
PC08	Soft decline	Additional authentication required
PE01	Transaction expired	The transaction could not be processed
PP99	General processor error	The transaction could not be processed

General

General errors (starting with E) indicate there is an issue at Buckaroo. We will investigate what is going wrong and fix where needed. This could be an internal error, or an unexpected communication failure with a payment processor.

Code	Explanation	Consumer Message
EB99	Internal error	The transaction could not be processed
EP99	Error communicating with processor	The transaction could not be processed