Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Finance / Finstar API
Finstar API logo

Finstar Ch Finstar API

66
AI ReadinessAI-Aware (B)66/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticFinanceBankingbearer9 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I want to initiate a SEPA payment from a Finstar business account, Check whether payment ID 4f3a-8b21 has settled yet, List all XS2A accounts under the current consent, Get the transaction history for account CH9300762011623852957 last month

Not supported: Does not handle KYC onboarding flows, ledger accounting, or merchant card acquiring - use for PSD2 payment initiation, account information, and card management only.

Jentic publishes the only available OpenAPI specification for Finstar API, keeping it validated and agent-ready. Finstar is a Swiss banking platform that provides PSD2-compliant open banking APIs for payment initiation (PIS), account information access (XS2A), card management, and digital onboarding for banks and fintechs. The 9-endpoint surface focuses on the highest-leverage operations a regulated agent or back-office system needs: authorize a session, initiate payments, list and inspect accounts, fetch transactions, and manage card settings.

Jentic One on GithubView OpenAPI Document

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.

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%2Ffinstar.ch%2Ffinstar" | sh
2

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%2Ffinstar.ch%2Ffinstar" | 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

List XS2A accounts and inspect balances for a consented end user

Retrieve transaction history for a specific account with date filtering

List issued cards and update card settings such as status and limits via PATCH /v1/cards/{cardId}

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

GET

/v1/cards

List issued cards

PATCH

/v1/cards/{cardId}

Update card settings

Jentic AI Readiness Score

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.

F

Finstar API

- AI-Aware (B)
66/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
44
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

44

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
32%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

89%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

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

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Finstar API by hand means learning its bearer auth, following the PSD2 authorize-then-initiate flow, and handling retries yourself. Through Jentic you install once, import Finstar from the API Directory, store the token once, and your agent calls it.

Permission scoping

Finstar covers payment initiation, account information, and card management, so limit the agent to the operations it needs, such as reading account transactions or listing cards, and leave payment initiation or card changes out of the allowed set unless the agent requires them. You choose which operations it may call.

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Fire Financial Services Business API

→

Irish business banking API with broader payment batch and webhook support

Choose when the agent needs Irish/UK business banking with payment batches; pick Finstar for Swiss XS2A and PSD2 PIS

Complementary

Firebase Auth REST API

→

Adds end-user authentication and identity to a banking app built on Finstar

Use Firebase Auth for end-user login alongside Finstar for the underlying banking operations

Complementary

Fintel API

→

Brings investment-side market intelligence to complement Finstar's banking primitives

Pair when an agent needs both transactional banking and equity ownership data

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.

GET STARTED

Start building with Finstar API

Explore with Jentic One
View OpenAPI Document