canonical: https://jentic.com/apis/swaggerhub.afterbanks/arcopay-api-psd2-eng

# Afterbanks Arcopay API PSD2 ENG

API standardization for a real-time connection to bank accounts. The API exposes 21 endpoints.

## For AI agents

Programmatically list of supported banks, it manages the consent retrieval by the end user.. Covers 21 operations.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- List of supported banks
- It manages the consent retrieval by the end user.
- Consent delete.
- Renew existing consent
- Global position and transactions up to a given date.
- Get the name of the bank linked to a specific IBAN.

## Use cases

### Finance and Accounting Operations

Use the Arcopay API PSD2 ENG to perform finance operations programmatically. The API provides 21 endpoints covering core functionality including list of supported banks, it manages the consent retrieval by the end user., consent delete..

Example prompt: Call GET /listOfSupportedBanks/ to list of supported banks

### Automated Accounts Management

Automate accounts operations by combining multiple Arcopay API PSD2 ENG endpoints. Agents can it manages the consent retrieval by the end user. and then consent delete. in a single workflow.

Example prompt: Call POST /consent/get/ to it manages the consent retrieval by the end user., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Arcopay API PSD2 ENG endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'list of supported banks', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /listOfSupportedBanks/ | List of supported banks |
| POST | /consent/get/ | It manages the consent retrieval by the end user. |
| POST | /consent/cancel/ | Consent delete. |
| POST | /consent/renew/ | Renew existing consent |
| POST | /consent/info/ | Consent information |
| POST | /transactions/ | Global position and transactions up to a given date. |
| POST | /ibanToService/ | Get the name of the bank linked to a specific IBAN. |
| GET | /transactions/categories/ | Categories list. Only for those servicekey that include this option. |

## Key resources

- **Accounts** — Operations for accounts
- **Batch** — Operations for batch
- **Bulkpayment** — Operations for bulkPayment
- **Consent** — Operations for consent
- **Directpayment** — Operations for directPayment

## Why Jentic

- **Setup:** Wiring the Arcopay API PSD2 ENG by hand means calling apipsd2.arcopay.io for its bank list, consent, and transaction operations and building each consent and transaction request yourself. Through Jentic you install once, import the Arcopay API PSD2 ENG from the API Directory, store any required credential once, and your agent calls it.
- **Permission scoping:** The Arcopay PSD2 API takes its targets in the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as listing supported banks or reading transactions. Every operation the agent can run is one you have added to its allowed set, so consent cancellation is included only if you add it.
- **Credential handling:** Any Arcopay API PSD2 ENG credential 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.
- **Discovery method:** Agents search Jentic by intent such as 'list supported banks' or 'get account transactions', and Jentic returns the matching Arcopay API PSD2 ENG operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the Arcopay API PSD2 ENG use?

The Arcopay API PSD2 ENG uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list of supported banks with the Arcopay API PSD2 ENG?

Yes. Use the GET /listOfSupportedBanks/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Arcopay API PSD2 ENG?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list of supported banks through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list of supported banks'. Jentic returns the matching Arcopay API PSD2 ENG operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Arcopay API PSD2 ENG have?

The Arcopay API PSD2 ENG exposes 21 endpoints covering accounts, batch, bulkpayment operations.

### Can I limit what my agent is allowed to do with the Arcopay PSD2 API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Arcopay operations and credentials the agent may use, and the Arcopay PSD2 API passes its targets in the request body rather than the URL path, so you scope access per operation. You can allow only the operations the agent needs, such as GET /listOfSupportedBanks/ to list supported banks or POST /transactions/ to read a global position and transactions, while leaving out others. Every operation the agent can run is one you have added to its allowed set, so a destructive call like POST /consent/cancel/ is available only if you explicitly grant it.