Finstar Ch Finstar API

Name: Finstar API
Brand: Finstar API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer9 EndpointsREST

For Agents

Initiate PSD2 payments, list accounts and transactions under XS2A consent, and manage Finstar-issued cards through a regulated Swiss open-banking API.

Install Jentic One Beta

Connect the Finstar API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Finstar 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.

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

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 instance

Jentic 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 Finstar API.

Authorize a PSD2 session and exchange consent for a bearer access token via /v1/authorize

Initiate Single Euro Payments Area (SEPA) and Swiss payment instructions through /v1/payments

Track payment status by paymentId until settlement or rejection

GET STARTED

Start building with Finstar API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Finstar API for, with concrete tasks.

★ PSD2 Payment Initiation

Initiate outbound payments under PSD2 PIS rules via /v1/payments and track lifecycle through /v1/payments/{paymentId}. Finstar handles strong customer authentication redirects and ASPSP routing, so the agent only manages the request, status polling, and reconciliation. A typical PIS integration is live in under a week.

POST to /v1/payments with debtor account, creditor IBAN, amount EUR 250, and reference 'INV-9081', then poll /v1/payments/{paymentId} until status is SETTLED

Account Aggregation under XS2A

Aggregate balances and transactions across consented accounts using /v1/accounts and /v1/accounts/{accountId}/transactions. The endpoints return PSD2-standard balance types and booked/pending transactions, suitable for treasury dashboards, cashflow forecasting, and AISP-licensed budgeting apps. Most teams ship a working aggregation prototype in 2-3 days.

List all accounts via GET /v1/accounts then fetch transactions for each account from the last 30 days and compute net cash flow

Card Lifecycle Management

Manage Finstar-issued cards through GET /v1/cards, GET /v1/cards/{cardId}, and PATCH /v1/cards/{cardId} to inspect cards and update status, limits, or controls. Useful for fraud response (immediate block on suspicious activity) and self-service card controls in a banking app. PATCH operations apply within seconds.

PATCH /v1/cards/card_42 with status=BLOCKED to immediately freeze a reported-stolen card

AI Agent Treasury Operations

Connect Finstar to an AI agent through Jentic so it can answer cashflow questions and initiate authorised payments using natural language. Jentic exposes /v1/payments and /v1/accounts as discoverable tools while keeping the bearer token in the vault, suitable for treasury copilots and finance assistants. Get started with Jentic One, the self-hosted execution layer

Through Jentic, search 'initiate a SEPA payment', load the /v1/payments schema, and execute a payment of EUR 100 from the operating account to a verified payee

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for finstar api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/authorize

Exchange PSD2 consent for an access token

POST

/v1/payments

Initiate a payment under PSD2 PIS

GET

/v1/payments/{paymentId}

Get payment status

GET

/v1/accounts

List XS2A accounts under consent

GET

/v1/accounts/{accountId}/transactions

Get account transactions

GET

/v1/cards

List issued cards

PATCH

/v1/cards/{cardId}

Update card settings

POST

/v1/authorize

Exchange PSD2 consent for an access token

POST

/v1/payments

Initiate a payment under PSD2 PIS

GET

/v1/payments/{paymentId}

Get payment status

GET

/v1/accounts

List XS2A accounts under consent

GET

/v1/accounts/{accountId}/transactions

Get account transactions

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Finstar token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'initiate a payment' or 'get account transactions', and Jentic returns the matching Finstar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Finstar API through Jentic.

Why is there no official OpenAPI spec for Finstar API?

Finstar does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Finstar API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Finstar API use?

Finstar uses HTTP bearer authentication. Clients first obtain a token via POST /v1/authorize, then send it in the Authorization header. Through Jentic, the bearer token is stored encrypted and injected at execution time.

Can I initiate SEPA payments with the Finstar API?

Yes. POST /v1/payments accepts SEPA and other supported payment types under PSD2 PIS rules and returns a paymentId for status tracking via GET /v1/payments/{paymentId}.

What are the rate limits for the Finstar API?

Finstar applies PSD2-standard rate limits at the consent level (typically four AISP polls per day per resource without user presence). Specific quotas depend on your contract; Jentic surfaces 429 responses as standard errors so agents can back off.

How do I aggregate accounts through Jentic?

Search Jentic for 'list bank accounts', load the /v1/accounts schema, and execute under a valid Finstar consent token. Then fan out to /v1/accounts/{accountId}/transactions for each returned account to build a cashflow view.

Can the Finstar API block a card immediately?

Yes. PATCH /v1/cards/{cardId} with a status change applies within seconds, making it suitable for fraud-response flows triggered by an agent or rules engine.

Can I limit what my agent is allowed to do with the Finstar API?

Yes. Because you run Jentic One yourself, your own rules decide which Finstar operations and credentials the agent may use. The Finstar API covers payment initiation, account information, and card management, so you can allow only read operations such as listing accounts via GET /v1/accounts or fetching transactions, while withholding state-changing calls like POST /v1/payments or PATCH /v1/cards/{cardId} unless the agent genuinely needs them. The stored bearer token is injected at execution time only for the operations you have permitted.

Finstar Ch Finstar API

Connect the Finstar API to your agent

Capabilities

Start building with Finstar API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs