canonical: https://jentic.com/apis/swaggerhub.afterbanks/arcopay-psd2-api # Afterbanks Arcopay PSD2 API La estandarización de la conexión con cualquier banco en tiempo real. The API exposes 22 endpoints. ## For AI agents Programmatically listado bancos, gestiona la obtención del consentimiento por parte del usuario final.. Covers 22 operations. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Listado bancos - Gestiona la obtención del consentimiento por parte del usuario final. - Borra un consentimiento. - Renueva un consentimiento existente - Información sobre el consentimiento - Posición global y movimientos hasta una fecha dada. - Obtención del nombre del banco vinculado a un IBAN concreto. ## Use cases ### Payments Operations Use the Arcopay PSD2 API to perform payments operations programmatically. The API provides 22 endpoints covering core functionality including listado bancos, gestiona la obtención del consentimiento por parte del usuario final., borra un consentimiento.. Example prompt: Call GET /listOfSupportedBanks/ to listado bancos ### Automated Accounts Management Automate accounts operations by combining multiple Arcopay PSD2 API endpoints. Agents can gestiona la obtención del consentimiento por parte del usuario final. and then borra un consentimiento. in a single workflow. Example prompt: Call POST /consent/get/ to gestiona la obtención del consentimiento por parte del usuario final., then verify the result ### AI Agent Integration via Jentic AI agents discover and call Arcopay PSD2 API 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 'listado bancos', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /listOfSupportedBanks/ | Listado bancos | | POST | /consent/get/ | Gestiona la obtención del consentimiento por parte del usuario final. | | POST | /consent/cancel/ | Borra un consentimiento. | | POST | /consent/renew/ | Renueva un consentimiento existente | | POST | /consent/info/ | Información sobre el consentimiento | | POST | /transactions/ | Posición global y movimientos hasta una fecha dada. | | POST | /ibanToService/ | Obtención del nombre del banco vinculado a un IBAN concreto. | | GET | /transactions/categories/ | Listado de categorías. Solo para las servicekeys con la opción contratada. | ## 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 PSD2 API 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 PSD2 API 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 PSD2 API 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 PSD2 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### What authentication does the Arcopay PSD2 API use? The Arcopay PSD2 API 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 listado bancos with the Arcopay PSD2 API? 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 PSD2 API? 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 listado bancos through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'listado bancos'. Jentic returns the matching Arcopay PSD2 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Arcopay PSD2 API have? The Arcopay PSD2 API exposes 22 endpoints covering accounts, batch, bulkpayment operations. ### Can I limit what my agent is allowed to do with the Arcopay PSD2 API? Yes. Because you run Jentic One yourself, your own rules decide which Arcopay PSD2 operations and credentials the agent may use, and the API takes its targets in the request body rather than the URL path, so you scope by operation. You add only the operations the agent needs, such as GET /listOfSupportedBanks/ to list supported banks or POST /transactions/ to read account movements, and everything else stays off limits. A sensitive operation like POST /consent/cancel/ is available to the agent only if you explicitly add it to the allowed set.