Adyen Data Protection API
Browse all Adyen APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readySecurityComplianceapiKey, basic1 EndpointsREST
For Agents
Submit GDPR right-to-erasure requests to Adyen for a specific shopper, removing payment and personal data tied to past transactions and returning an audit reference.
Use for: I need to honour a GDPR right-to-be-forgotten request for a customer, Submit a Subject Erasure Request to Adyen, Delete a shopper's payment data after account closure, Trigger removal of saved card and address data for a former customer
Not supported: Does not handle data export, consent capture, or marketing preferences - use for GDPR Subject Erasure Request submission only.
Submit GDPR Subject Erasure Requests against shopper data held by Adyen, including payment details, delivery addresses, and shopper email addresses tied to past transactions. The API exposes a single operation that records the erasure request and returns a unique request reference for audit and follow-up. Designed for merchants that need a programmatic way to satisfy Article 17 right-to-be-forgotten obligations.
Install Jentic One Beta
Connect the Adyen Data Protection API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Data Protection API, 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-data-protection-service" | sh2
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-data-protection-service" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Data Protection API.
Submit a GDPR Subject Erasure Request against a specific shopper or PSP reference
Receive an Adyen-generated request reference for audit logging and downstream tracking
Trigger erasure across linked payment, address, and shopper email records held by Adyen
Authenticate erasure submissions with X-API-Key or basic auth web service user credentials
Surface validation errors when the requested record is not found or cannot be erased
Use Cases
Patterns agents use Adyen Data Protection API for, with concrete tasks.
★ GDPR Right-to-Erasure Workflow
Honour Article 17 right-to-be-forgotten requests by forwarding shopper data deletions to Adyen as part of a wider data erasure pipeline. The single /requestSubjectErasure operation accepts a merchantAccount, shopperReference, and optional pspReference list, and returns the request status with an Adyen-side reference. The merchant remains responsible for orchestrating erasures across other systems (CRM, email, analytics) but the API removes the Adyen footprint.
POST /requestSubjectErasure with merchantAccount TestMerchant and shopperReference cust_8421, then log the returned response code and reference in the privacy ledger
Customer Account Closure Pipeline
Tie Adyen data erasure into the workflow that runs when a customer permanently closes their account on a merchant platform. Once outstanding obligations and refunds are settled, the closure pipeline calls /requestSubjectErasure to remove saved card tokens, billing addresses, and shopper email data from Adyen. The returned reference is stored as evidence of compliance for the retention period required by the merchant's privacy policy.
After confirming the customer has no open balances, POST /requestSubjectErasure for shopperReference cust_3092 and store the response in the privacy_audit table for at least seven years
AI Agent Privacy Compliance
AI agents that handle inbound privacy requests can submit Adyen erasures through Jentic without holding raw API credentials. The agent searches for 'submit a GDPR erasure request' via Jentic, receives the /requestSubjectErasure schema with required merchantAccount and shopperReference fields, executes the call, and returns the resulting reference to the privacy team for audit. Credentials remain isolated in your Jentic One instance throughout.
Search Jentic for 'submit Adyen subject erasure request', load the schema, then POST /requestSubjectErasure with the merchantAccount and shopperReference resolved from the privacy ticket
Key Endpoints
1 endpoints — submit gdpr subject erasure requests against shopper data held by adyen, including payment details, delivery addresses, and shopper email addresses tied to past transactions.
METHOD
PATH
DESCRIPTION
POST
/requestSubjectErasure
Submit a Subject Erasure Request against a shopper or PSP reference
POST
/requestSubjectErasure
Submit a Subject Erasure Request against a shopper or PSP reference
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 Data Protection API
- Foundational (D-)42/100
100
Foundational Compliance69
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability30
Security50
AI DiscoverabilityPowered 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.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
0%
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.
21
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
52%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
33%
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).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Adyen Data Protection API by hand means handling its X-API-Key or basic auth and targeting the classic CA host for a single GDPR erasure call. Through Jentic you install once, import the Data Protection API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Data Protection takes the shopper reference in the request body rather than a resource id in the URL path, so you limit the agent to the single operation it needs, the subject erasure request. Because you pick the operations, this surface exposes nothing beyond that erasure call.
Credential isolation
Your Adyen X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'submit a GDPR erasure request' or 'delete shopper payment data', and Jentic returns the requestSubjectErasure 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
Stripe API
Stripe handles GDPR erasure through its dashboard and Forget Customer mutation rather than a dedicated REST endpoint
Choose Stripe if your processor is already Stripe; Adyen Data Protection only applies to data Adyen holds
FAQs
Specific to using Adyen Data Protection API through Jentic.
What authentication does the Adyen Data Protection API use?
The Data Protection API accepts an API key in the X-API-Key header or HTTP Basic authentication with web service user credentials. Generate the key from your Adyen Customer Area. Through Jentic, the X-API-Key value is held encrypted in your Jentic One instance and agents authenticate with scoped tokens, so the raw key stays out of agent context.
Can I delete only specific transactions for a shopper?
Yes. POST /requestSubjectErasure accepts a pspReference list alongside the shopperReference, so you can scope the erasure to specific PSP references rather than every record tied to that shopper. Omitting pspReference triggers a broader erasure of records linked to the shopperReference.
What are the rate limits for the Data Protection API?
Rate limits are tied to your Adyen contract and are typically low because erasure is a low-volume operation. Excess requests return HTTP 429. For bulk migrations or large account closures, batch the work over time and contact your Adyen account manager if you need a temporary increase.
How do I submit an erasure request through Jentic?
Search Jentic for 'submit Adyen subject erasure request' to find the POST /requestSubjectErasure operation. Required fields are merchantAccount and shopperReference, with optional pspReference list and forceErasure flag. Jentic loads the schema and executes with vaulted credentials. Run it through Jentic One, the self-hosted execution layer.
Does an erasure request remove data from my own systems too?
No. The Data Protection API only triggers erasure of records held inside Adyen - payment details, shopper addresses, and emails tied to transactions. You remain responsible for erasing data in your CRM, analytics platform, email tooling, and any other downstream system that holds personal data.
Can I limit what my agent is allowed to do with the Adyen Data Protection API?
Yes. This API exposes a single operation, the subject erasure request (POST /requestSubjectErasure), and because you run Jentic One self-hosted you decide which operations and credentials your agent may use. You can restrict the agent to just that erasure call, so it cannot reach anything beyond submitting a Subject Erasure Request. The shopper reference travels in the request body rather than a URL path, and your own rules govern which merchant accounts and credentials it is permitted to use.
GET STARTED