Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Payments / Adyen / Adyen Recurring API (deprecated)
Adyen Recurring API (deprecated) logo

Adyen Recurring API (deprecated)

Browse all Adyen APIs
51
AI ReadinessFoundational (C-)51/100
See full scorecard
Official vendor OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey, basic6 EndpointsREST

For Agents

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

Use for: List all stored payment tokens for a shopper, Disable a stored card token so future charges fail, Create a permit allowing a third party to charge a stored token, Revoke a previously issued permit on a stored token

Not supported: Does not authorise card payments, run payouts, or manage account holders - use only for managing stored payment tokens, permits, and Account Updater on the classic integration.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Adyen Recurring API (deprecated) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Recurring API (deprecated), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-recurring" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-recurring" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

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

Ask the card issuer to push a payment notification to the shopper via POST /notifyShopper

Use shopperReference and recurringDetailReference identifiers to operate on stored tokens

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

POST

/notifyShopper

Trigger an issuer-driven shopper notification

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Adyen Recurring API (deprecated)

- Foundational (C-)
51/100
100
Foundational Compliance
70
Developer Experience & Jentic Compatibility
31
AI-Readiness & Agent Experience
94
Agent Usability
30
Security
77
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

70

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
3%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

31

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
58%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

17%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

48%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

30

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
30%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

77

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring this deprecated Adyen Recurring API by hand means handling its X-API-Key or basic auth, targeting the classic PAL host, and managing stored tokens and permits yourself. Through Jentic you install once, import the Recurring API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Recurring API takes the shopper reference in the request body rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as listing stored tokens for a shopper. Because you pick the operations, disabling a token or a permit stays out unless you include it.

Credential isolation

Your Adyen X-API-Key and basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list stored tokens for a shopper' or 'disable a recurring token', and Jentic returns the matching Recurring operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Adyen Recurring API?

Yes. Because Jentic One is self-hosted and your own rules decide which operations and credentials the agent may use, you choose exactly which Recurring API calls it can make. If you only want it listing a shopper's stored tokens, you expose POST /listRecurringDetails and leave POST /disable, POST /createPermit, POST /disablePermit, POST /scheduleAccountUpdater, and POST /notifyShopper out. Since the API takes the shopperReference in the request body rather than a resource id in the path, you scope the agent by the operations you grant rather than by URL, and your Adyen key is injected at execution time so it never reaches the agent's prompt or context.

GET STARTED

Start building with Adyen Recurring API (deprecated) API

Explore with Jentic One
View OpenAPI Document