Error Messages
When the requested operation cannot be completed, Rapyd returns an error code with a message.
The message explains the cause of the error and the steps to correct it.
Note
A third-party integration, such as an external 3DS service, may trigger different errors in the sandbox and production environments.
For a list of all Rapyd error codes and messages, see Rapyd Error Codes.
The response usually includes the error. See Response Format.
Note
Certain errors have different formats. These errors may appear in the response, a webhook, or both. For example:
Card Network Errors - Card processing errors.
Merchant Advice Codes - Related to Create Payment response parameters:
merchant_advice_code
andmerchant_advice_message
.
Response Format
When a requested operation succeeds, the response has two objects: status
(see the table below) and data
. The data
object contains the response parameters documented for each method.
When the requested operation fails and returns an error, the response has one object: status
The status
object contains information about the requested operation, including error data.
Parameter | Type | Description | Value Example |
---|---|---|---|
| string | Error code. Summarizes what went wrong. Same as response_code. Empty when successful. | ERROR_INVALID_EWALLET |
| string | Status of the request. One of the following:
| ERROR |
| string | Detailed error message:
Empty when successful. | The request attempted an operation that requires a wallet, but the wallet was not recognized. The request was rejected. Corrective action: Use the ID of a valid wallet, a string starting with 'ewallet_'. |
| string | Error code. Summarizes what went wrong. Same as error_code. Empty when successful. | ERROR_INVALID_EWALLET |
| string | Operation ID for Rapyd Support. UUID. | c9ef7f0c-07e0-4c85-9491-5d517920fb04 |
Response Example: Success
{ "status": { "error_code": "", "status": "SUCCESS", "message": "", "response_code": "", "operation_id": "f338792d-548f-48a9-ab50-aa64d969a8b3" }, "data": { "id": "payment_e9bf3b2355931a063384a6704244a345", // . . . "merchant_advice_message": null } }
Response Example: Error
{ "status": { "error_code": "ERROR_INVALID_EWALLET", "status": "ERROR", "message": "The request attempted an operation that requires a wallet, but the wallet was not recognized. The request was rejected. Corrective action: Use the ID of a valid wallet, a string starting with 'ewallet_'.", "response_code": "ERROR_INVALID_EWALLET", "operation_id": "c9ef7f0c-07e0-4c85-9491-5d517920fb04" } }