Open banking API: payments, account data and MCP
One API for account-to-account payments and bank data, callbacks with statuses, an MCP server for AI agents and a ready-made consent widget. Write to [email protected] and we send you sandbox keys.
How to start
- Step 01
Write to us
At [email protected]: who you are and what you are building. We send back an apiKey and a token for the sandbox.
- Step 02
Connect to the sandbox
The api.sandbox.fizen.com sandbox has test banks that simulate login and SCA. It runs 8:00-18:00 UTC, with no IP restrictions.
- Step 03
Make your first call
Initiate a payment or fetch transactions from a test account. Statuses arrive by webhook at your URL.
Sandbox keys
Today we issue them by email, after a short conversation. Production keys after verifying your company.
API products
| Product | What it does | Typical use |
|---|---|---|
| Payments (PIS) | Initiates a transfer from the payer's account, approved in their banking app. | Checkout, recurring, deferred and bulk payments |
| Data (AIS) | Provides balances, transactions and account holder data with the user's consent. | Scoring, customer verification, accounting, matching |
| MCP | A Model Context Protocol server that gives AI agents read-only access to account data. | AI assistants for individuals, businesses and accounting firms |
| Fizen Connect | A ready-made widget: bank selection, consent and account selection. You embed it in your app. | The fastest integration without building your own consent UI |
| Webhooks | Notifications about payment and consent status changes and new transactions. | Updating orders and balances without polling the API |
Payments (PIS)
- What it does
- Initiates a transfer from the payer's account, approved in their banking app.
- Typical use
- Checkout, recurring, deferred and bulk payments
Data (AIS)
- What it does
- Provides balances, transactions and account holder data with the user's consent.
- Typical use
- Scoring, customer verification, accounting, matching
MCP
- What it does
- A Model Context Protocol server that gives AI agents read-only access to account data.
- Typical use
- AI assistants for individuals, businesses and accounting firms
Fizen Connect
- What it does
- A ready-made widget: bank selection, consent and account selection. You embed it in your app.
- Typical use
- The fastest integration without building your own consent UI
Webhooks
- What it does
- Notifications about payment and consent status changes and new transactions.
- Typical use
- Updating orders and balances without polling the API
Code samples
The samples are illustrative. Exact paths and fields are in the documentation.
curl -X POST "https://api.sandbox.fizen.com/[payment initiation path]" \ -H "apiKey: [YOUR_API_KEY]" \ -H "token: [YOUR_TOKEN]" \ -H "Content-Type: application/json" \ -d '{ "amount": "149.00", "currency": "PLN", "description": "Order 10482", "recipientIban": "[recipient IBAN]", "redirectUrl": "https://your-shop.com/payment/return" }'curl "https://api.sandbox.fizen.com/[transactions list path]?accountId=[account ID]&dateFrom=2026-10-01" \ -H "apiKey: [YOUR_API_KEY]" \ -H "token: [YOUR_TOKEN]"{ "mcpServers": { "fizen": { "type": "http", "url": "https://mcp.fizen.com" } }}<script src="[Fizen Connect script URL]"></script><div id="fizen-connect"></div><script>FizenConnect.mount('#fizen-connect', { sessionId: '[session ID from the API]' })</script>Documentation and tools
- Bank coverageThe list of banks with the AIS and PIS rollout stage.
- PricingData from PLN 0, payments at 0.5% per transaction, no fixed fees.
- DocumentationGuides, quickstart and flow descriptions.
- API referenceEvery endpoint, field and error code.
- ChangelogAPI changes and new banks.
- GitHubSample integrations and SDKs [if available].
- PostmanA ready collection for the sandbox.
How to get production keys
Verification usually takes 3 business days. We require it because our services are supervised by the KNF (data as an AIS provider, payments with a licensed partner), so we must know the company and the purpose for which it uses data and payments.
- Step 01
Agreement and company verification
You sign the agreement, send your company registration data and name the ultimate beneficial owner.
- Step 02
Use case description
You describe what you use payments or data for and how you inform users about consent.
- Step 03
Production setup
You submit IP addresses for the whitelist and webhook URLs, and receive production keys.
What to prepare
- Company registry entry, tax ID and a technical contact
- Ultimate beneficial owner information
- A description of the flow and the consent screens shown to users
- Fixed IP addresses of the servers that call the API
- Webhook URL (HTTPS)
Developer questions
What are the rate limits?
By default [N] requests per minute per key. For higher volumes we raise the limit after a conversation. In addition, PSD2 limits fetching data without the user present to 4 times a day per account.
What happens 180 days after consent is given?
AIS consent is valid for 180 days under PSD2. Before it expires we send a webhook, and the user renews consent with a single confirmation in their bank (SCA). Without renewal, data access expires.
Do you support business accounts?
Yes, but the scope depends on the bank: some banks expose business accounts reliably, others with limitations (for example only one banking user). The current status per bank is on the Banks page.
What format is the data in?
The REST API returns JSON over HTTPS, and webhooks are JSON too. Transactions use a unified format regardless of the bank. Schemas are in the API reference.
Which banks are in the sandbox?
The sandbox has test banks that simulate login, SCA, multiple accounts and typical errors, so you can test the whole flow without a real account. The list of test banks is in the documentation.
Try Fizen on your own data
We set up business accounts and API keys after a short conversation: tell us what you do and we reply within one business day. For yourself, you can start right away.