Adyen Test Cards API

Name: Adyen Test Cards API API
Brand: Adyen Test Cards API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsTesting QaapiKey, basic1 EndpointsREST

For Agents

Generate custom Adyen test card number ranges for QA scenarios that the standard test cards do not cover.

Quickstart

Get started with Adyen Test Cards API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Adyen custom test card range"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adyen Test Cards API API.

Generate one or more custom test card ranges via POST /createTestCardRanges with brand, issuerCountry, and outcome

Cover specific 3D Secure 1 and 3DS2 outcomes for QA — Authorised, ChallengeShopper, IdentifyShopper, Refused

Simulate fundingSource (credit, debit, prepaid) and issuer country combinations not present in the standard test deck

Produce ranges suitable for automated regression suites that run against Adyen test endpoints

GET STARTED

Start building with Adyen Test Cards API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Adyen Test Cards API API for, with concrete tasks.

★ QA Regression Coverage for Edge Cases

Standard Adyen test cards cover the main happy paths. To reproduce a specific issuer country, fundingSource, or 3DS2 outcome, QA teams call POST /createTestCardRanges with the desired brand, issuerCountry, and resultCode, and receive a fresh PAN range. The new PANs are then used in regression suites to exercise that exact path against Adyen's test endpoint, ensuring future code changes do not regress the handling of that case.

Call POST /createTestCardRanges with brand=visa, issuerCountry=NL, fundingSource=debit, and the desired authorisationResultCode for the QA scenario

Developer Sandbox Setup

When a new developer joins the team, they need a deterministic set of test cards to exercise the integration in their local sandbox. POST /createTestCardRanges produces a deck tailored to the team's coverage matrix: one card per brand, one card per fundingSource, one card for every refusal reason the integration handles. The same call can be re-run any time to refresh the deck after Adyen's test environment is rotated.

Call POST /createTestCardRanges once per scenario in the team coverage matrix and store the resulting PANs in the team's secrets manager for use in sandbox runs

Refusal-Reason Simulation

Integrations need to handle every refusal reason Adyen can return — fraud block, expired card, do-not-honour, declined, suspected fraud, and more. POST /createTestCardRanges generates a card range for each refusal scenario by setting the appropriate refusalReason on the request. Tests then call POST /authorise on the Payment API or POST /payments on Checkout with the generated PAN to confirm the integration handles each refusal cleanly.

Call POST /createTestCardRanges with refusalReason=FRAUD to obtain a PAN that always returns Refused with a fraud reason, then exercise the full refusal-handling path

AI Agent Test Data Provisioning via Jentic

An automated test orchestration agent that prepares ephemeral test data per CI run searches Jentic for 'create Adyen custom test card range', loads the schema for /createTestCardRanges, and executes once per scenario in the test plan. Jentic injects X-API-Key from the encrypted vault and the resulting PANs are written to the CI run's secret store, never to disk.

Search Jentic for 'create Adyen custom test card range', load the createTestCardRanges schema, then execute once per scenario in the CI run's test plan

Key Endpoints

1 endpoints — the adyen test cards api generates custom test card number ranges for use in development and qa against adyen's test environment.

METHOD

PATH

DESCRIPTION

POST

/createTestCardRanges

Create one or more custom test card ranges

POST

/createTestCardRanges

Create one or more custom test card ranges

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Adyen API keys and basic-auth credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time — the raw X-API-Key value never enters the agent context, even when generating test data into a CI run.

Intent-based discovery

Agents search by intent (e.g., 'create a test card that returns 3DS2 challenge') and Jentic returns the createTestCardRanges operation with its full input schema, so the agent picks the right parameters without browsing Adyen's testing documentation.

Time to first call

Direct Adyen Test Cards integration: 1-2 hours for credential setup and request payload understanding. Through Jentic: under 15 minutes — search, load, execute one call per QA scenario.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Adyen Payment API

Authorise the test cards generated by this API in classic server-to-server flows

Use Payment API to call /authorise with a generated test PAN and verify the integration handles the resultCode correctly

Complementary

Adyen Checkout API

Use generated test cards in modern Checkout sessions and Drop-in

Use Checkout to test the front-end Drop-in or Components flow with custom PANs that trigger specific 3DS2 outcomes

Complementary

Adyen BIN Lookup API

Inspect the BIN attributes of a generated test card range

Use BIN Lookup to confirm a generated test PAN reports the issuerCountry, brand, and fundingSource you requested

Complementary

Adyen Disputes API

Test dispute and chargeback handling against generated test PANs

Use Disputes API in QA after running flows with custom test cards to exercise the dispute defence integration

FAQs

Specific to using Adyen Test Cards API API through Jentic.

What authentication does the Adyen Test Cards API use?

The API supports an API key in the X-API-Key header (ApiKeyAuth) and HTTP Basic auth (BasicAuth) using web-service user credentials, the same auth model as the rest of Adyen's classic-platform APIs. Through Jentic, the credential is held encrypted in the vault and only a scoped execution token is exposed to the agent.

What outcomes can I simulate with custom test cards?

POST /createTestCardRanges accepts parameters that set the brand, issuerCountry, fundingSource, authorisationResultCode, and refusalReason on the generated PAN range. This lets you generate test cards that always Approve, always Refuse with a specific reason, or trigger ChallengeShopper or IdentifyShopper for 3DS2 testing.

Can I use these test cards against the live Adyen environment?

No. Custom test card ranges generated by this API are valid only against Adyen's test endpoints, such as pal-test.adyen.com and checkout-test.adyen.com. They will not authorise on the live endpoints; the production environment uses real card credentials only.

How do I generate a custom test card with the Test Cards API through Jentic?

Search Jentic for 'create Adyen custom test card range', load the createTestCardRanges schema, then execute with brand, issuerCountry, fundingSource, and the desired authorisationResultCode. Jentic injects X-API-Key from the encrypted vault. Get an account at https://app.jentic.com/sign-up.

What are the rate limits for the Adyen Test Cards API?

Adyen does not publish a fixed numeric rate limit for the Test Cards API in the spec; usage is administrative and intended for occasional QA setup rather than per-transaction calls. If 429 responses appear, contact Adyen support to review the merchant account's quota.

How is this different from the standard Adyen test cards?

Adyen publishes a fixed list of standard test card PANs that cover the main approval and refusal paths. The Test Cards API generates custom ranges that fill specific gaps — a particular issuer country, a specific refusalReason, a 3DS2 step-up scenario — that the standard list does not include. Use it when the standard cards cannot reproduce a case your integration must handle.