Openbankingproject Ch Swiss NextGen Banking API-Framework
✓ Official Vendor SpecFinanceBankingbearer34 EndpointsREST
For Agents
Initiate Swiss bank payments, access account and balance information, and manage signing baskets through Berlin Group NextGenPSD2-compliant XS2A endpoints with redirect SCA.
Use for: I need to initiate a SEPA credit transfer from a Swiss customer account, Retrieve the balances for a customer's CHF account, List transactions on an authorised account for the past 30 days, Set up a signing basket containing three pending payments for one authorisation
Not supported: Does not handle card processing, in-store POS payments, or non-EEA jurisdictions — use for Berlin Group NextGenPSD2 XS2A flows in Switzerland and compatible markets only.
The Swiss NextGen Banking API-Framework is the Swiss edition of the Berlin Group NextGenPSD2 specification, defining a harmonised XS2A interface that banks (ASPSPs) and Third Party Providers can use to exchange payment, account, and consent data. It covers Payment Initiation Service (PIS), Account Information Service (AIS), Confirmation of Funds Service (PIIS), and Signing Baskets, plus shared common services for consent and authorisation. Strong Customer Authentication is supported through Redirect, Decoupled, Embedded, and OAuth approaches, though the obp.ch community recommends Redirect SCA. The framework underpins open banking interoperability for Swiss banks while remaining compatible with the wider Berlin Group ecosystem.
Install Jentic One Beta
Connect the Swiss NextGen Banking API-Framework to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Swiss NextGen Banking API-Framework, 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 Swiss NextGen Banking API-Framework API.
Initiate a single payment with payment-service and payment-product path parameters covering SEPA, instant, and cross-border instructions
Retrieve a list of accounts the customer has authorised through an AIS consent
Fetch balances and transaction history for a specific authorised account
Create and authorise a Signing Basket grouping multiple payment instructions for joint authorisation
Confirm whether sufficient funds exist on an account for a specified amount
Manage payment cancellation authorisations for in-flight payments
Use Cases
Patterns agents use Swiss NextGen Banking API-Framework API for, with concrete tasks.
★ Swiss XS2A Payment Initiation
Initiate Swiss SEPA, instant, and cross-border payments from customer accounts through a single Berlin Group NextGenPSD2 interface. The /v1/{payment-service}/{payment-product} endpoint accepts the payment service (e.g. payments, periodic-payments) and product (e.g. sepa-credit-transfers, instant-sepa-credit-transfers) as path segments, with Redirect SCA handling the customer authorisation step.
POST /v1/payments/sepa-credit-transfers with debtor IBAN CH9300762011623852957 and creditor IBAN DE89370400440532013000 for EUR 250, then redirect the user to the SCARedirect link returned in _links.
Account Aggregation
Aggregate balances and transactions across Swiss bank accounts after the customer authorises an AIS consent. The /v1/accounts, /v1/accounts/{account-id}, and /v1/accounts/{account-id}/balances endpoints expose the structured fields needed for personal finance dashboards and SME bookkeeping integrations without screen-scraping each bank's e-banking portal.
Read the active AIS consent ID, GET /v1/accounts to list authorised accounts, then GET /v1/accounts/{account-id}/balances for each to surface a unified balance view.
Signing Basket Approvals
Group multiple payment instructions into a Signing Basket so the customer authorises them in a single SCA flow rather than approving each payment individually. This streamlines bulk supplier payments and treasury batches in corporate banking integrations, with the basket lifecycle tracked through dedicated authorisation and status endpoints.
Create a signing basket referencing five pending sepa-credit-transfer payment IDs, then trigger authorisation and poll status until the basket is finalised.
AI Agent Cross-Bank Treasury
Through Jentic, an AI treasury agent can initiate payments and pull balances from any Swiss ASPSP that implements the obp.ch framework without learning each bank's portal. The agent searches for the right Berlin Group operation, loads the schema, and executes the call with bank-specific base URLs supplied via the catalogue.
Through Jentic, search for 'list Swiss bank accounts under an AIS consent', load GET /v1/accounts, and execute it with the active Consent-ID header to return all authorised accounts.
Key Endpoints
34 endpoints — the swiss nextgen banking api-framework is the swiss edition of the berlin group nextgenpsd2 specification, defining a harmonised xs2a interface that banks (aspsps) and third party providers can use to exchange payment, account, and consent data.
METHOD
PATH
DESCRIPTION
POST
/v1/{payment-service}/{payment-product}
Initiate a payment by service and product
GET
/v1/{payment-service}/{payment-product}/{paymentId}
Retrieve a payment and its content
GET
/v1/{payment-service}/{payment-product}/{paymentId}/status
Get the status of a payment
GET
/v1/accounts
List accounts authorised under an AIS consent
GET
/v1/accounts/{account-id}
Read details for a specific account
GET
/v1/accounts/{account-id}/balances
Retrieve balances for an account
POST
/v1/{payment-service}/{payment-product}/{paymentId}/authorisations
Start an authorisation sub-resource for a payment
POST
/v1/{payment-service}/{payment-product}
Initiate a payment by service and product
GET
/v1/{payment-service}/{payment-product}/{paymentId}
Retrieve a payment and its content
GET
/v1/{payment-service}/{payment-product}/{paymentId}/status
Get the status of a payment
GET
/v1/accounts
List accounts authorised under an AIS consent
GET
/v1/accounts/{account-id}
Read details for a specific account
GET
/v1/accounts/{account-id}/balances
Retrieve balances for an account
POST
/v1/{payment-service}/{payment-product}/{paymentId}/authorisations
Start an authorisation sub-resource for a payment
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth bearer tokens, eIDAS QWAC certificates, and per-ASPSP client credentials are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped operation access only — Swiss TPP secrets never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'initiate a Swiss SEPA payment' or 'fetch account balances under an AIS consent') and Jentic returns the matching Berlin Group operation with the Consent-ID, PSU-ID, and TPP-Redirect-URI headers it needs.
Time to first call
Direct integration: 4-8 weeks per ASPSP for QWAC, OAuth, redirect SCA, and basket lifecycle. Through Jentic: under a day for the integration code once TPP onboarding is complete.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Swiss NextGen Banking API-Framework API through Jentic.
What authentication does the Swiss NextGen Banking API use?
The spec declares an HTTP Bearer scheme (BearerAuthOAuth) — the TPP obtains an OAuth 2.0 access token and presents it in the Authorization header. On top of that, ASPSPs require eIDAS QWAC mTLS at the transport layer and the customer SCA flow (Redirect, Decoupled, Embedded, or OAuth) for payment and consent authorisations. Through Jentic, the access token and certificates stay isolated in MAXsystem.
Can I initiate a SEPA instant credit transfer with this API?
Yes. POST /v1/payments/instant-sepa-credit-transfers initiates an instant SEPA credit transfer; the same path pattern accepts other payment products such as sepa-credit-transfers, target-2-payments, and cross-border-credit-transfers. The Swiss edition refines message formats and adds Switzerland-specific examples while remaining compatible with Berlin Group v1.3.4.
What are the rate limits for the Swiss NextGen Banking API?
The framework itself does not mandate a single rate limit — each implementing Swiss ASPSP defines its own quotas, typically published in its developer portal. AIS reads of balances and transactions are usually limited to four unattended pulls per day per consent under PSD2 norms; PIS calls are limited per TPP rather than per consent.
How do I list authorised accounts through Jentic?
Search Jentic for 'list authorised Swiss bank accounts', load GET /v1/accounts, and execute it with the active Consent-ID header from the AIS consent flow. Jentic returns the structured account list so the agent can iterate through each account-id and call /balances or /transactions without parsing the obp.ch sandbox responses.
Is the Swiss NextGen Banking API free?
The framework specification is open and free to consume. Calling live ASPSP endpoints requires TPP authorisation under PSD2/equivalent Swiss regulation, eIDAS QWAC certificates, and per-bank onboarding — costs sit with that registration and certificate process rather than with the spec itself.
Can I cancel a payment after submission?
Yes for payments that have not yet executed: the spec exposes /v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations to start a cancellation authorisation sub-resource. Once an instant SEPA payment has settled it cannot be reversed through this API — settlement is irrevocable and any reversal requires an out-of-band recall.
GET STARTED