Creditas Cz Creditas PSD2 Accounts API
60
AI ReadinessAI-Aware (B-)60/100
Community OpenAPI document · agent-readyFinanceBankingoauth2, mutualTLS3 EndpointsREST
Install Jentic One Beta
Connect the Creditas PSD2 Accounts API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Creditas PSD2 Accounts 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%2Fcreditas.cz%2Fcreditas" | 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%2Fcreditas.cz%2Fcreditas" | 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 Creditas PSD2 Accounts API.
List a client's payment accounts under AISP consent
Read the current balance of a specific account
Retrieve an account's transaction history
Operate within PSD2 account-information scopes
Use Cases
Patterns agents use Creditas PSD2 Accounts API for, with concrete tasks.
★ Account aggregation
Personal-finance and treasury tools aggregate balances across banks. The Creditas PSD2 API lists a client's payment accounts and returns each balance under AISP consent, so an aggregator can show a current position for Creditas holdings.
List the client's Creditas accounts and read each account's current balance
Transaction reconciliation
Bookkeeping systems reconcile ledger entries against bank transactions. The API returns an account's transaction history so a reconciliation job can match entries and flag discrepancies.
Retrieve the transaction history for an account and match it against ledger entries
Agent-driven balance check
A finance assistant can answer balance questions under consent. Through Jentic, an agent uses the PSD2 token and certificate to list accounts and read balances in response to a user request.
Under AISP consent, list a client's accounts and summarize their balances for the user
Key Endpoints
3 endpoints — the creditas psd2 accounts api is a european open-banking (aisp) interface from the czech bank creditas.
METHOD
PATH
DESCRIPTION
GET
/v1/my/accounts
List a client's payment accounts
GET
/v1/my/accounts/{accountId}/balance
Get an account balance
GET
/v1/my/accounts/{accountId}/transactions
Get account transactions
GET
/v1/my/accounts
List a client's payment accounts
GET
/v1/my/accounts/{accountId}/balance
Get an account balance
GET
/v1/my/accounts/{accountId}/transactions
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Creditas needs an OAuth2 authorization-code token and a mutual TLS client certificate before any read. With Jentic One you install once, import the three operations from the API Directory, and both credential layers are wired in one place.
Permission scoping
Accounts are addressed by an account id in the path, so you can scope an agent to specific accounts and to read-only balance and transaction operations.
Credential isolation
Your OAuth2 secret and the client certificate are stored encrypted by your own Jentic One instance and used only at execution time, so they never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents find the right account operation through Jentic's intent search, matching a request like showing an account's transactions to the matching Creditas endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Creditas PSD2 Accounts API through Jentic.
How does the Creditas PSD2 API authenticate?
It uses two layers: an OAuth2 authorization-code token carrying AISP account scopes, plus a mutual TLS (mutualTLS) client certificate for the connection. Jentic One manages both and injects them at execution time.
Can I limit what my agent can do with the Creditas API?
Yes. Because each account is addressed by an account id in the path, you can scope an agent to read-only operations and even to specific accounts, keeping balances and transactions separate from any write access elsewhere.
What is AISP access under PSD2?
AISP is the account-information service role under PSD2: with the customer's consent it grants read access to accounts, balances, and transactions, but not the ability to move money.
Can this API initiate payments?
No. These endpoints are account-information only; payment initiation under the PISP role is out of scope for this interface.
Why does Creditas require a client certificate?
PSD2 mandates mutual TLS between the bank and a licensed third party, so a client certificate authenticates the connection in addition to the OAuth2 token.
GET STARTED