Abnamro Payment Initiation (PSD2)
★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth2, apiKey, http8 EndpointsREST
For Agents
Initiate, execute, cancel, and check the status of SEPA and cross-border payments from ABN AMRO accounts under PSD2. Requires PSD2 license, EIDAS certificate, OAuth, and API key.
Use for: I need to register a SEPA payment from an ABN AMRO account, Execute a payment after the customer has authorised it, Cancel a future-dated SEPA payment before it runs, Check the status of payment ID 8325P3346070108S0PD
Not supported: Does not handle account information retrieval, standing orders, bulk payments, or card acquiring — use for single SEPA and cross-border payment initiation only.
Jentic publishes the only available OpenAPI specification for ABN AMRO's Payment Initiation (PSD2) API, keeping it validated and agent-ready. The Payment Initiation (PSD2) API lets licensed Third Party Payment service providers (TPPs) initiate single SEPA and cross-border payments from ABN AMRO accounts, gated by PSD2 consent. The 8 endpoints cover registering a payment, executing it after consent, cancelling a future-dated payment, and checking status, for both SEPA and cross-border flows. Authentication combines OAuth 2.0 (client credentials and authorization code), an API key, and a QWAC EIDAS certificate.
Install Jentic One Beta
Connect the Payment Initiation (PSD2) to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payment Initiation (PSD2), 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Payment Initiation (PSD2) API.
Register a SEPA credit transfer for an ABN AMRO account holder to authorise
Register a cross-border credit transfer in non-EUR or outside the euro zone
Execute a registered payment after the account holder consents
Cancel a future-dated SEPA or cross-border payment before execution
Check the status of a SEPA payment by paymentId
Check the status of a cross-border payment by paymentId
Use Cases
Patterns agents use Payment Initiation (PSD2) API for, with concrete tasks.
★ TPP-Initiated SEPA Payments
Licensed PISPs initiate SEPA credit transfers from a customer's ABN AMRO account on the customer's behalf. POST /sepa-credit-transfers registers the payment, the customer authorises it via the ABN AMRO consent flow, and PUT /sepa-credit-transfers/{paymentId} executes it. GET on the status sub-resource returns the SEPA result codes (ACCC, ACSC, RJCT) for reconciliation.
Register a SEPA credit transfer of EUR 100.01 from NL62ABNA9999841479 to NL12ABNA9999876523, then execute the payment after consent and confirm status ACCC
Cross-Border Credit Transfers
Non-EUR or out-of-SEPA-zone payments use the cross-border endpoints. POST /cross-border-credit-transfers registers the payment with creditor agent and address, PUT executes after consent, and GET status returns the result. The two-step register-and-execute model means the customer keeps full control of the consent before the funds move.
Register a USD 1000 cross-border payment to a US account with full creditor address and execute once consent is granted
Payment Cancellation and Status Checks
Operations and reconciliation flows cancel future-dated payments and confirm settlement status. DELETE /sepa-credit-transfers/{paymentId} and DELETE /cross-border-credit-transfers/{paymentId} cancel future-dated payments before execution; the GET status endpoints return the live result so a backend can reconcile expected vs actual outcomes.
Cancel future-dated SEPA payment 8325P3346070108S0PD and confirm status reflects the cancellation
Agent-Driven PISP Workflow via Jentic
Licensed PISP backends benefit from a single tool surface that an AI agent or service can call. Through Jentic, an agent searches for a payment intent, loads the matching ABN AMRO operation, and executes with the OAuth/API-key credentials held in the Jentic vault. EIDAS certificate handling stays at the network layer; Jentic isolates the OAuth and API-key secrets.
Search Jentic for 'register a SEPA payment', load the ABN AMRO PSD2 schema, and execute the registration call with the customer's payment details
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for abn amro's payment initiation (psd2) api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/sepa-credit-transfers
Register a SEPA credit transfer
PUT
/sepa-credit-transfers/{paymentId}
Execute a registered SEPA payment
DELETE
/sepa-credit-transfers/{paymentId}
Cancel a future-dated SEPA payment
GET
/sepa-credit-transfers/{paymentId}/status
Get SEPA payment status
POST
/cross-border-credit-transfers
Register a cross-border credit transfer
PUT
/cross-border-credit-transfers/{paymentId}
Execute a cross-border payment
GET
/cross-border-credit-transfers/{paymentId}/status
Get cross-border payment status
POST
/sepa-credit-transfers
Register a SEPA credit transfer
PUT
/sepa-credit-transfers/{paymentId}
Execute a registered SEPA payment
DELETE
/sepa-credit-transfers/{paymentId}
Cancel a future-dated SEPA payment
GET
/sepa-credit-transfers/{paymentId}/status
Get SEPA payment status
POST
/cross-border-credit-transfers
Register a cross-border credit transfer
PUT
/cross-border-credit-transfers/{paymentId}
Execute a cross-border payment
GET
/cross-border-credit-transfers/{paymentId}/status
Get cross-border payment status
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
ABN AMRO OAuth client secrets and API keys are stored encrypted in the Jentic vault. Agents call operations by ID and Jentic mints access tokens at execution time. The EIDAS QWAC certificate is configured at the network layer; Jentic isolates the OAuth and API-key material from the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'register a SEPA payment') and Jentic returns POST /sepa-credit-transfers along with its input schema, including the debtor, creditor, amount, and execution date fields.
Time to first call
Direct integration: 1-3 weeks to set up PSD2 licensing, EIDAS certificate handling, OAuth client credentials and authorization code flows, and the consent redirect. Through Jentic: under a day for the API surface itself, with EIDAS and licensing handled separately as required by PSD2.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Stripe's payment processing platform for cards, wallets, and bank debits.
Choose Stripe for merchant card acquiring and subscriptions; ABN AMRO PSD2 for direct bank-account payment initiation under PSD2.
FAQs
Specific to using Payment Initiation (PSD2) API through Jentic.
Why is there no official OpenAPI spec for ABN AMRO Payment Initiation (PSD2)?
ABN AMRO publishes the API reference as a YAML/HTML page rather than a hosted OpenAPI catalog. Jentic generates and maintains this spec so that AI agents and developers can call ABN AMRO's Payment Initiation (PSD2) API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the ABN AMRO Payment Initiation (PSD2) API use?
The API uses OAuth 2.0 client credentials for payment registration and OAuth 2.0 authorization code (with the ABN AMRO consent application) for execution, plus an API key passed as API-Key, plus a QWAC EIDAS certificate for mTLS. Through Jentic, OAuth and API-key secrets are kept in the Jentic vault; the EIDAS certificate is handled at the network layer.
Can I initiate cross-border payments with the ABN AMRO PSD2 API?
Yes. POST /cross-border-credit-transfers registers a non-EUR or out-of-SEPA payment with creditor name, account, agent, and address. After consent, PUT /cross-border-credit-transfers/{paymentId} executes the payment, and GET /cross-border-credit-transfers/{paymentId}/status returns the result.
How do I check the status of a SEPA payment through Jentic?
Search Jentic for 'check SEPA payment status' to find GET /sepa-credit-transfers/{paymentId}/status, load the schema, and execute with the paymentId returned at registration. Status codes ACCC and ACSC indicate success, RJCT indicates rejection, and PDNG indicates pending.
What licensing do I need to use the API in production?
Production use requires a PSD2 license (or FCA license for UK access), an EIDAS QWAC certificate (or OBWAC for UK), and a registered production app on the ABN AMRO Developer Portal. The sandbox is open to any developer for integration testing with static fictive data.
Can I cancel a payment after it has been executed?
Only future-dated payments can be cancelled. DELETE /sepa-credit-transfers/{paymentId} or DELETE /cross-border-credit-transfers/{paymentId} cancels a registered future-dated payment before its execution date; once executed, cancellation is no longer possible through the API.
GET STARTED