Fio banka

Fio banka is a Czech bank with a token-authenticated API for account movements and payment orders. Agents pull new transactions and statements, track card transactions, and stage domestic, euro, and foreign payments or whole batches, which a person then authorizes in internet banking.

Verified 12 actions API key available

Fio banka website Platform Documentation Capability data verified 2026-08-25

A schedule fires the nightly reconciliation pass

Get New Transactions returns everything since the last download and advances Fio's marker

The agent records every movement and its id before it processes any of them

Each incoming payment's variable symbol is matched against open invoices

Matched receipts post to the ledger and the invoice is closed

Unmatched credits are posted with the payer, the amount, and the symbols they carried

A person names the invoice behind each unmatched credit, or decides where to rewind the marker

What This Integration Enables

Fio banka's token API is a small surface with a clear opinion about where software stops. It gives you a movement feed, the bank's own numbered statements, and a chute for payment orders. What it does not give you is the ability to release money. An imported order becomes a batch that an authorized person approves by SMS or Fio signature in internet banking, and the API has no route that completes that step. The bank ships the pause.

That makes Fio unusually well matched to how FlowRunner already works. FlowRunner agents pull new movements on a schedule, read a statement as the signed document an auditor asks for, and itemize the merchant card fees the netted movement list hides. They assemble domestic, euro, and foreign payment orders, each with the fields Fio requires for that shape, and submit them as a batch that a person authorizes. The human-in-the-loop step on the payment path is not an option this connector adds. It is the bank's design, and it lines up with ours.

Without FlowRunner

Statements downloaded by hand Someone exports a movement list every morning and pastes it into the reconciliation sheet

Payments matched by eye The variable symbol is read off the row and compared with an invoice list in another window

Gaps found at close A day of movements that never got processed is discovered weeks later, during the month end review

With FlowRunner

Movements collected exactly once The scheduled read uses Fio's own download marker, so nothing is fetched twice or missed silently

Matching by the field designed for it The agent matches on the variable symbol first and only escalates what does not resolve

Gaps surfaced the same night A break between the marker and the ledger is raised as a decision, with the movement ids on both sides

Use Case Scenarios

Incoming payments matched on the variable symbol

A Czech domestic payment carries three numbers that are not free text. The variable symbol is conventionally the invoice number, the specific symbol identifies the payer, and the constant symbol classifies the purpose. On a schedule the agent calls Get New Transactions, stores every movement and its id, and matches each credit's variable symbol against the open invoices in Xero or a ledger staged in Google Sheets. Matched receipts close their invoice. Credits with no symbol, or a symbol that matches nothing, are posted into Slack with the payer and amount so a person can name the invoice.
A supplier run assembled by an agent and released by a person

Approved supplier bills reach the agent from the accounting system. It sorts them into the three shapes Fio recognizes, filling the domestic account and bank code for local suppliers, the IBAN and beneficiary name for euro payments, and the BIC, full address, remittance line, and charge allocation that a foreign payment requires. Create Payment Batch submits them in the order Fio insists on, since a file in the wrong order is rejected whole. The batch then sits in internet banking waiting for a signature. The agent posts the total, the count, and the charge allocation on the foreign lines so the signatory knows what they are approving.
The statement an auditor will actually accept

Movements are a query. A statement is Fio's own numbered accounting document, and its numbering restarts each year. On a schedule the agent calls Get Last Statement Number, compares it with what has already been filed, and downloads anything new with Get Statement in PDF form so the signed document is what gets archived. The file lands in document storage with the year and number in its name, and a note posts to the finance channel. For merchant accounts, Get Merchant Card Transactions is pulled alongside it, because it is the only place the fee split is itemized rather than netted.

Human-in-Loop Highlight

Get New Transactions moves a marker on Fio's servers as a side effect. When the answer contains movements, the server records a new position, and those movements are never returned by that route again. If a flow reads and then fails before storing what it read, the data is gone from the feed. The recovery is Set Last Transaction ID, which rewinds the marker to a movement id you name, or Set Last Date for a coarser rewind to a day. Both are irreversible in the other direction, because setting the marker forward skips movements permanently and the only way back is a period read. So the agent never picks the rewind point. It reports what it can prove: "Marker sits at movement 2847113. The last movement written to the ledger is 2847098. Fifteen movements are unaccounted for. Rewind to 2847098 and risk re-posting anything already booked, or rewind to the start of the day and reconcile by hand?" A person answers. The agent then runs Get Transactions By Period, which touches nothing, to show exactly what falls in the gap before anything is replayed.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

12 actions

Movements

Get Transactions By Period Returns the account movements between two dates and leaves Fio's download marker alone. The safe read for reconciliation, development, and anything that may be run twice.
Get New Transactions Returns everything since the last successful download. It advances the marker whenever the answer contains movements, which gives exactly once delivery as long as the flow stores what it read.
Get Statement Returns one official numbered bank statement. Available as a PDF, which is the signed document itself.
Get Last Statement Number Returns the year and number of the most recent statement. How a flow notices a new statement exists without guessing at numbers.
Get Merchant Card Transactions Returns a merchant terminal's card transactions with the fee breakdown per transaction. The only place the fee split is visible rather than netted into one figure.

Markers

Set Last Transaction ID Moves the download marker to a movement id you name, so the next read starts after it. The precise recovery after a failed run, and permanent in the forward direction.
Set Last Date Moves the download marker to a date. The coarser recovery, for when the day processing broke is known but the exact movement is not.

Payments

Import Payment Orders Uploads a file of payment orders. It does not pay anyone. Fio groups the orders into a batch that a person authorizes in internet banking, and the response is XML that must be read for a refusal rather than trusted for its status code.
Create Domestic Payment Submits a single Czech domestic payment, building the order for you. The account is the domestic form with a separate bank code rather than an IBAN, and the variable symbol is what the recipient reconciles against.
Create Euro Payment Submits a SEPA euro payment. The IBAN and the beneficiary's name are both required, and the instant payment type settles in seconds rather than the next business day.
Create Foreign Payment Submits a non SEPA international payment. Far more is mandatory here, including the BIC, the beneficiary's full address, a remittance line, the payment reason, and the charge allocation that decides who absorbs the correspondent bank fees.
Create Payment Batch Submits a mixed batch in one call and sorts the orders into the sequence Fio requires. Sending them in any other order has the whole file rejected.

Frequently Asked Questions

What can FlowRunner do with Fio banka?

FlowRunner agents can run Get Transactions By Period, Get New Transactions, and Get Statement in Fio banka, plus 9 more actions.

Does connecting Fio banka to FlowRunner require OAuth?

No. Fio banka connects to FlowRunner with an API key, no OAuth flow required.

Can Fio banka trigger a FlowRunner workflow automatically?

Fio banka doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Fio banka

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us