canonical: https://jentic.com/apis/creditas.cz/creditas

# Creditas Cz Creditas PSD2 Accounts API

The Creditas PSD2 Accounts API is a European open-banking (AISP) interface from the Czech bank Creditas. Under PSD2 account-information scopes, an authorized integration can list a client's payment accounts, read the balance of a specific account, and retrieve the transaction history for an account. Access requires an OAuth2 authorization-code token and a mutual TLS (mutualTLS) client certificate.

## For AI agents

Lets an AI agent read a Creditas client's payment accounts, balances, and transactions under PSD2 AISP consent.

## Scope

Does not initiate payments, open accounts, or issue cards: use it to read Creditas accounts, balances, and transactions under PSD2 AISP only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Under AISP consent, list a client's accounts and summarize their balances for the user

## Key endpoints

| 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 |

## Key resources

- **Accounts** — List a client's payment accounts under AISP consent
- **Balances** — Read the current balance of a specific account
- **Transactions** — Retrieve an account's transaction history

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 44 / 100
  - Developer Experience & Jentic Compatibility: 79 / 100
  - AI-Readiness & Agent Experience: 59 / 100
  - Agent Usability: 94 / 100
  - Security: 45 / 100
  - AI Discoverability: 54 / 100
- **View full report:** https://jentic.com/apis/creditas.cz/creditas/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Nordigen (GoCardless Bank Account Data)** — Pan-European open-banking account data aggregator
- **Plaid** — Account and transaction data across many institutions
- **Enable Banking** — PSD2 aggregation layer across European banks

## FAQ

### 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.