Adyen Recurring API (deprecated)

Name: Adyen Recurring API (deprecated) API
Brand: Adyen Recurring API (deprecated)
Availability: InStock

✓ Official Vendor SpecPaymentsBilling SubscriptionsapiKey, basic6 EndpointsREST

For Agents

List, disable, and permit-manage Adyen stored payment tokens for subscription billing on classic integrations.

Quickstart

Get started with Adyen Recurring API (deprecated) 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:
"list Adyen stored payment tokens for a shopper"

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

Capabilities

What an agent can do with Adyen Recurring API (deprecated) API.

List stored payment tokens for a shopper via POST /listRecurringDetails

Disable a stored token to stop future charges via POST /disable

Issue a third-party permit against a token via POST /createPermit and revoke one via POST /disablePermit

Trigger a card-update sweep on stored tokens via POST /scheduleAccountUpdater

GET STARTED

Start building with Adyen Recurring API (deprecated) API

Explore with Jentic

View OpenAPI Spec

The Adyen Recurring API is the classic-integration surface for managing stored payment tokens (recurring details), permits that grant third parties limited charging rights against those tokens, and ancillary tasks such as scheduling Account Updater runs and notifying shoppers. The six endpoints cover listing stored details for a shopperReference, disabling a token, creating and revoking permits, and asking the issuer to push a payment notification to the shopper. Adyen has deprecated this API for new integrations and recommends the Checkout API stored payment methods endpoints instead; the Recurring API remains live for existing classic integrations.

Use Cases

Patterns agents use Adyen Recurring API (deprecated) API for, with concrete tasks.

★ Subscription Token Lifecycle

Subscription merchants on Adyen's classic integration store a payment token at first charge, then list it via POST /listRecurringDetails when the customer logs in to manage billing. POST /disable removes a token when the customer cancels or replaces a card, ensuring future renewal attempts fail cleanly rather than authorising on stale data. POST /scheduleAccountUpdater requests Adyen to push expired or replaced card numbers from the issuers, reducing involuntary churn.

Call POST /listRecurringDetails with shopperReference and merchantAccount, then call POST /disable with the chosen recurringDetailReference when the shopper cancels

Third-Party Permits for Marketplace Charging

When a marketplace seller needs to charge a buyer's stored card on the marketplace platform, POST /createPermit issues a scoped permit referencing a shopper's recurringDetailReference, with restrictions such as profile, currency, or amount cap. POST /disablePermit revokes the permit later. This is the classic-platform mechanism for delegated charging without sharing the underlying token.

Call POST /createPermit with shopperReference, recurringDetailReference, and a permit object specifying restrictAccount and amount cap

Issuer-Initiated Shopper Notifications

Some markets require advance notice before a stored card is charged. POST /notifyShopper instructs the card issuer to push a notification to the shopper through their banking app or SMS for the upcoming recurring debit. This supports compliance with mandate rules in regions where issuer-driven shopper notifications are the standard, and improves charge success by reducing dispute rates.

Call POST /notifyShopper with shopperReference, recurringDetailReference, amount, and merchantAccount to request issuer-driven shopper notification

AI Agent Token Management via Jentic

A subscription operations agent that needs to disable tokens for cancelled customers searches Jentic for 'disable an Adyen stored payment token', loads the schema for /disable, and executes per cancelled subscription. Jentic injects X-API-Key from the encrypted vault. The agent never sees the raw secret and confirms each disable succeeded by checking the response code.

Search Jentic for 'disable an Adyen stored payment token', load the disable schema, then execute one call per cancelled subscription with shopperReference and recurringDetailReference

Key Endpoints

6 endpoints — the adyen recurring api is the classic-integration surface for managing stored payment tokens (recurring details), permits that grant third parties limited charging rights against those tokens, and ancillary tasks such as scheduling account updater runs and notifying shoppers.

METHOD

PATH

DESCRIPTION

POST

/listRecurringDetails

List stored payment tokens for a shopper

POST

/disable

Disable a stored payment token

POST

/createPermit

Create a third-party permit

POST

/disablePermit

Revoke a permit

POST

/scheduleAccountUpdater

Refresh expired card tokens

POST

/notifyShopper

Trigger an issuer-driven shopper notification

POST

/listRecurringDetails

List stored payment tokens for a shopper

POST

/disable

Disable a stored payment token

POST

/createPermit

Create a third-party permit

POST

/disablePermit

Revoke a permit

POST

/scheduleAccountUpdater

Refresh expired card tokens

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.

Intent-based discovery

Agents search by intent (e.g., 'list stored tokens for a shopper' or 'disable a recurring token') and Jentic returns listRecurringDetails or disable with its full input schema, so the agent picks the right endpoint without browsing classic-integration docs.

Time to first call

Direct Adyen Recurring integration: 1-3 days for credential setup, token lifecycle handling, and Account Updater wiring. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adyen Checkout API

Modern stored payment methods endpoints replace the deprecated Recurring API

Use Checkout's /storedPaymentMethods for any new tokenisation and recurring charging integration

Complementary

Adyen Payment API

Charge stored tokens via /authorise on the classic Payment API

Use Recurring to manage tokens and Payment to charge them in a classic server-to-server integration

Complementary

Adyen BIN Lookup API

Determine card properties before charging a stored token

Pair with Recurring to inspect card brand, country, or fundingSource for a stored token before deciding to charge

Complementary

Adyen Disputes API

Defend chargebacks raised against recurring charges

Use Disputes after Recurring when subscribers chargeback recurring debits and you need to upload defence evidence

FAQs

Specific to using Adyen Recurring API (deprecated) API through Jentic.

What authentication does the Adyen Recurring 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. Through Jentic, the credential is held encrypted in the vault and only a scoped execution token is exposed to the agent at runtime.

Can I list stored cards for a shopper with the Adyen Recurring API?

Yes. POST /listRecurringDetails returns the stored payment tokens (recurringDetailReference values) attached to a shopperReference, along with their metadata such as last-four digits and contract type. Use this to render a saved-cards UI or to choose a token before a recurring charge.

Is the Adyen Recurring API still recommended for new integrations?

No. Adyen has marked Recurring as deprecated and recommends the Checkout API stored payment methods endpoints (/storedPaymentMethods) for new integrations. Existing classic integrations continue to work, and this enrichment covers the v68 surface for those integrations.

How do I disable a stored token with the Adyen Recurring API through Jentic?

Search Jentic for 'disable an Adyen stored payment token', load the disable schema, then execute with shopperReference, recurringDetailReference, and merchantAccount. 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 Recurring API?

Adyen does not publish a fixed quantitative rate limit for Recurring in the spec; usage is generally administrative and not per-transaction. If 429 responses appear in production, contact Adyen support to review the merchant account's quota.

What is a permit on the Recurring API?

A permit is a scoped charging right against a stored token, issued via POST /createPermit. It can be restricted by merchant account, amount, currency, or profile, and is used in classic platform setups where one entity stores the token and another charges against it. POST /disablePermit revokes a permit before its natural expiry.