Adyen Gateway Tests – Help & Reference

This document describes the Adyen Gateway Tests: a set of test scenarios used to verify how your integration handles different payment outcomes when using the Adyen gateway (e.g. via Gr4vy). Each scenario triggers a specific result code and refusal reason so you can test error handling, retries, and user messaging.

What are the Adyen Gateway Tests?

The Adyen Gateway Tests cover the main failure and non-success outcomes returned by Adyen. For each scenario you can:

• Confirm your system receives the expected result code (e.g. Refused, Error, Received, Cancelled).
• Confirm the refusal reason (e.g. Blocked Card, Expired Card) when applicable.
• Validate that your order management, retry logic, and customer-facing messages behave correctly for each case.

The tests are executed by sending a payment request (e.g. via Gr4vy Create Transaction) with a specific holder name value. The gateway uses that value to simulate the corresponding response.

How the tests work

• Each test uses the same payment request template (amount, currency, card details, etc.).
• The only change per test is the cardholder / holder name (e.g. in buyer.billing_details.first_name when using Gr4vy). That value tells the Adyen test environment which scenario to return.
• The response will contain the resultCode and refusalReason (when applicable) for that scenario.

Full list of Adyen Gateway Tests

The table below lists all supported test scenarios: the test name, the expected result code, the refusal reason (if any), the holder name value used in the request, and the internal test code.

Adyen-recommended merchant actions

The following table summarizes Adyen’s recommended actions for each response code when you encounter these responses in production. It is based on Adyen’s Refusal reasons and Result codes documentation.

Important: Adyen recommends that you do not expose the detailed refusal reason or refusal reason code to shoppers (e.g. in UI or logs visible to them), to avoid misuse. Use the recommended action to decide behaviour; show the shopper a generic, safe message (e.g. “Payment could not be completed. Please try again or use another card or payment method.”) where appropriate.

General (from Adyen):

• Refused: Inform the shopper the payment was refused and ask them to try again (e.g. with a different payment method or card).
• Error: Inform the shopper there was an error processing the payment.
• Cancelled: Inform the shopper the payment was cancelled and check if they want to continue with their order.
• Received / Pending: Inform the shopper you received their order and are waiting for the final payment status; rely on webhooks for the final outcome.

Obtaining the Postman collection

A Postman collection is available that runs all Adyen Gateway Tests (one request per scenario) using the correct request format and holder name values.

To obtain the Postman collection for the Adyen Gateway Tests, please contact your Account Manager. They can provide the collection file and any required environment or authentication details.

Related information

• Use a test/sandbox environment when running these scenarios.
• Responses and exact wording may vary slightly by gateway version and configuration; the table above reflects the standard Adyen test behaviour.
• For gateway-specific or environment-specific questions, contact your Account Manager or support channel.