konfipay

konfipay by windata is a German corporate banking gateway that reaches bank accounts over EBICS. Agents manage bank accounts and balances, trigger EBICS jobs, create and submit payment files, and track their status through the bank.

Verified 83 actions Session available

konfipay website Platform Documentation Capability data verified 2026-08-25

The ERP produces a SEPA payment file for the weekly supplier run

Create Payment File uploads it with Submit set to false, so nothing leaves the building

Extract Payments From File splits it into individually editable payments

Get Payment File VoP Report returns each payee name checked against their bank's record

The agent posts every close match and no match with its payee, IBAN, and amount

Treasury clears or drops each flagged line before Submit Payment File transmits it

What This Integration Enables

konfipay is not a bank and not a card processor. It is the gateway that carries a German corporate's payment files and statement requests to the banks' data centers over EBICS, which means one connection covers every bank relationship rather than one integration per bank. Two design decisions run through the whole API and both of them suit agent work. Payments are created before they are submitted, so there is a stage where they exist, can be edited, and can still be deleted. Transactions, statement files, documents, and PayPal activity all arrive marked new and stay new until something acknowledges them, which gives exactly once processing with no date arithmetic.

FlowRunner agents register bank accounts and read their balances, force a fresh EBICS download rather than trusting the last scheduled one, and build, stage, submit, and track payments and payment files through to the bank's own verdict. They reconcile a payment file against the statement entries the bank later produced, ingest PayPal turnover in the same shape as bank turnover for a single cash position, and manage the account's users, groups, keys, and scopes. Submitting a payment sends a real file to a real bank, and once it has gone it cannot be edited or deleted. That is the boundary the human-in-the-loop step on this connector is built around.

Without FlowRunner

A file with no review step The ERP writes a payment file and somebody uploads it, with the first real check happening at the bank

Name mismatches found later A payee whose name does not match their account is discovered after the money has gone

Statements read twice or not at all Polling by date leaves gaps and duplicates, and reconciliation drifts from what the bank actually sent

With FlowRunner

A staged file that can still be changed The file is uploaded unsent, split into editable lines, and corrected before anything transmits

Name mismatches raised before sending The payee verification report is read on the staged file and the exceptions go to a person

An inbox that empties exactly once New transactions are listed, processed, then acknowledged, so nothing is read twice or skipped

Use Case Scenarios

A supplier run staged, checked, then sent

The ERP writes a SEPA file. The agent uploads it with Create Payment File and Submit set to false, since that route otherwise sends on the upload call. Extract Payments From File splits the file into individually editable payments, which is the edit path for a file the ERP produced and cannot easily regenerate. The agent reads Get Payment File VoP Report, drops or corrects what treasury flags, and only then calls Submit Payment File. Afterward, List Payment Files is polled for the processing status, because that field is where a rejection by the gateway or by the bank appears, and a rejection posts into Slack with the file and the reason.
Reconciliation that covers the bank and PayPal together

Freshness on this platform comes from the EBICS job rather than from the read, so the agent calls Trigger EBICS Job for booked transactions, polls Get EBICS Job Status, and reads only once it reports finished. It then lists transactions marked new, matches them against open items in SAP Business One or NetSuite, and calls Acknowledge Transactions for the page it processed, remembering that acknowledgment covers one page rather than the whole result set. A connected PayPal account is read through the same new and acknowledge pattern, so one flow produces a single cash position across both.
Did the payroll run actually leave the account

A payment file was submitted on Friday and finance wants proof rather than an assumption. The agent calls Get Payment File Transaction Matches, which returns the bank statement entries the gateway has paired with the file once the bank confirmed execution. An empty answer here is not a failure, it means nothing has matched yet, so the agent distinguishes the two and keeps polling instead of raising an alarm. When the matches complete, the confirmation and the matched totals are written into Google Sheets and the treasury channel gets a one line summary naming the file, the count, and the value.

Human-in-Loop Highlight

Verification of Payee is the strongest signal this platform can give you that money is about to reach the wrong person, and it is deliberately advisory. Get Payment File VoP Report reads, on a staged file that has not been sent, whether each payee's name matches the account holder their own bank has on record. A close match or a no match is exactly the shape a redirected invoice takes: right IBAN, subtly wrong name. Nothing in the API blocks a submission over it. And the undo does not exist, because once a file is submitted it cannot be edited or deleted, only recalled by telephoning the bank, and Delete Payment works solely on a payment that has not yet gone. So the supplier run agent stages, reads the report, and stops. It posts: "Payment file SUP-2026-14, 61 lines, 248,900 EUR. Two lines returned no match: Meridian Bau GmbH on DE44 5001, 18,400 EUR, and Halbach Systeme, 6,120 EUR. Drop both and submit the other 59, or hold the file?" Treasury answers. The other 59 lines were never the question.

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

83 actions

Authentication and Scopes

List Assigned Scopes Returns the scopes this connection's key actually holds. The first thing to run when anything answers with a permission error, since every resource family is scope gated.
List Available Scopes Returns every scope the platform defines, whether or not this key holds it. Useful when issuing a key, because a new key cannot exceed the scopes of the key that created it.

EBICS

List EBICS Contacts Returns the bank connections held on the account, the credentials through which the gateway actually talks to each bank.
Trigger EBICS Job Forces a scheduled download to run now. The fetch my bank data immediately operation, covering booked statements, the intraday view, payment status reports, and documents.
Get EBICS Job Status Reports whether a triggered job is scheduled, running, finished, or failed. Read only once it reports finished, or the answer is yesterday's data wearing today's timestamp.

Bank Accounts

Add Bank Account Registers a bank account. The account number, bank code, and BIC are derived from the IBAN, so they rarely need sending.
Update Bank Account Changes a registered account. It merges rather than replaces, so missing elements keep their existing values and partial updates are safe.
List Bank Accounts Returns the registered accounts. It defaults to active production accounts only, which is usually why an account seems to be missing.
Get Bank Account Returns one registered account with its holder, its agreement document, and its flags.
Get Bank Account Balances Returns an account's balances over a period. The cash position read, drawn from the statements the gateway has downloaded.
Get Bank Account Agreement Document Returns the mandate paperwork held for an account, which the bank requires before it will act on instructions.
Remove Bank Account Deletes an account from the gateway. Asynchronous, so the response is an operation id rather than a completed deletion.
Get Bank Account Delete Status Reports whether an asynchronous account deletion has completed.

Payments

Create Payments Creates SEPA credit transfers or direct debits. They stay pending, editable, and deletable, because nothing leaves the building on this call.
Submit Payments Turns pending payments into SEPA files and sends them to the bank. This is the operation that moves money.
List Payments Searches payments by status, type, amount, execution date, end to end id, or either party's IBAN. Filtering by payment file id is the documented way to read a file's individual lines.
Get Payment Returns one payment with its amount, parties, execution date, and submission state.
Delete Payment Removes a pending payment before it is sent. It works only before submission, since a submitted payment is already at the bank.
Create Payment File Uploads a SEPA or cross border payment file. It submits by default, so set the submit flag to false when the file needs review first.
Submit Payment File Transmits a file that was uploaded unsent. The force option re-sends a file that already went and is restricted to files the bank rejected, because forcing an accepted file pays everyone twice.
Extract Payments From File Splits an uploaded file into individually editable payments. The edit path for a file the ERP produced, and the original file is not kept afterward.
List Payment Files Returns your payment files with their processing status. The status field is where a payment's fate appears, whether rejected by the gateway or by the bank.
Get Payment File Returns one file's metadata and processing status.
Get Payment File Content Returns a file's original content exactly as the gateway holds it.
Get Payment File Transaction Matches Returns the bank statement entries matched to a payment file after the bank confirmed execution. This is how a flow answers whether a payroll run actually left the account, and an empty answer means nothing has matched yet rather than that something failed.
Get Payment File VoP Report Returns the Verification of Payee results for a file, whether each payee's name matched the account holder their bank has on record. Readable before a staged file is sent.
Delete Payment File Removes a file and every payment inside it. Only an unprocessed file can be deleted.

Transactions

List Transactions Returns transactions from the statements the gateway has downloaded. It defaults to booked entries, so pending intraday activity is a separate request.
Get Transaction Returns one transaction in full.
Acknowledge Transactions Confirms a page of transactions has been processed so it stops coming back as new. It covers one page, and there is no way to un-acknowledge, so acknowledge after the work rather than before.

Transaction Files

List Transaction Files Returns the statement files downloaded from the banks across the camt, SWIFT, and PDF formats. It defaults to the booked statement format.
Get Transaction File Returns one statement file's metadata, including its format, account, creation time, and new flag.
Get Transaction File Content Returns a statement file in its original format.
Acknowledge Transaction File Confirms a statement file has been processed. Downloading the content does not do this.

Documents

Submit Document Sends an arbitrary document to a bank's data center over EBICS. The gateway does not look inside it, so a structural mistake surfaces at the bank rather than here.
List Documents Returns banking documents outside the standard statement and payment flow.
Get Document Returns one banking document's metadata.
Get Document Content Returns a document's content in its original format.
Acknowledge Document Confirms a banking document has been processed so it stops appearing as new.

Reference

Get Bank Information Looks up a financial institution by its German bank code or its BIC. Worth calling before registering an account.
List Exchange Rate Providers Returns the foreign exchange providers the gateway can draw on. It publishes the provider list only, not rates.

PayPal

Add PayPal Account Connects a PayPal business account so its transactions are readable like bank statements. The start fetch date applies once and cannot be replayed, so anything earlier is never imported.
Update PayPal Account Changes a connected account. The client secret is required on every call and is never returned, so it has to be held elsewhere.
List PayPal Accounts Returns the connected PayPal accounts.
Get PayPal Account Returns one connected account.
Remove PayPal Account Disconnects an account and permanently deletes its transactions and refunds with it. Deactivating instead keeps the history.
List PayPal Transactions Returns a connected account's transactions, with the same new and acknowledge pattern as bank turnover.
Get PayPal Transaction Returns one transaction, optionally re-fetching it from PayPal first so a changed status is visible.
Acknowledge PayPal Transaction Confirms a PayPal transaction has been processed.
Refund PayPal Transaction Refunds a captured payment. Leaving the amount empty issues a full refund, which is the vendor's own instruction and less error prone than assembling the figure.
List PayPal Refunds Returns the refunds made on an account over a period.
List PayPal Balances Returns an account's balance history. Read beside the bank balances, it gives one cash position across both.

Payment Providers

List Payment Providers Returns the third party payment providers the gateway recognizes.
Add Payment Provider Account Registers an account with one of those providers so its data can be pushed in.
Update Payment Provider Account Changes a registered provider account's name or provider.
List Payment Provider Accounts Returns the registered provider accounts.
Remove Payment Provider Account Deletes a provider account and its payloads.
Create Payment Provider Payload Stores a block of provider data as base64 inside a JSON request.
Create Payment Provider Payload Raw Stores a block of provider data sent as the raw request body. The better route for anything large or binary.
List Payment Provider Payloads Returns the payloads stored for a provider account, with the same new and acknowledge pattern.
Get Payment Provider Payload Returns one payload's metadata and its encoded content.
Get Payment Provider Payload Raw Returns a payload's decoded content served with the content type it was stored under.
Update Payment Provider Payload Changes a stored payload's content or classification.
Acknowledge Payment Provider Payload Confirms a payload has been processed so it stops appearing as new.

Account

Get Account Returns the account this API key belongs to, optionally including its users and groups in the same call.
Create Account Creates an account and emails its administrator an invitation. Restricted to the vendor's integration partners.
Delete Account Requests deletion of an account. Deferred by thirty days and restricted to integration partners.
Revoke Account Deletion Cancels a pending deletion inside that thirty day window.
List Related Accounts Returns the accounts related to this one, typically the ones it created.

API Keys

Create API Key Issues a new key. The full value is returned exactly once, in this response, and every later read shows it masked.
Update API Key Changes a key's name or scopes. It cannot show the key value again.
List API Keys Returns the account's keys, every value masked after the first characters.
Delete API Key Revokes a key. It refuses to delete the key making the request, which is a useful guard against a flow locking itself out.

Users

Create User Adds a user to the account. They cannot sign in until an invitation is accepted.
Update User Changes a user's name or group membership. The email address is changed through the two step token route instead.
List Users Returns the account's users with their status, which is the field that explains a user who says they cannot log in.
Get User Returns one user with their status, authentication method, and groups.
Invite User Emails a user their invitation, which is what lets them set a password. Also the fix for an invitation that never arrived.
Request Email Change Token Emails a verification token to a user's current address. Step one of changing their email, which means someone locked out of the old address cannot use this route.
Change User Email Sets the new email address using that token. The email is part of their sign in credentials.
Delete User Removes a user. The vendor states a deleted user cannot be restored.
List User Groups Returns the account's user groups. Group membership is how permissions are actually assigned.
List User Group Users Returns the users in one group. The quick answer to who can approve payments, without reading every user.

Frequently Asked Questions

What can FlowRunner do with konfipay?

FlowRunner agents can run List Assigned Scopes, List Available Scopes, and List EBICS Contacts in konfipay, plus 80 more actions.

Does connecting konfipay to FlowRunner require OAuth?

No. konfipay connects to FlowRunner with session-based authentication, no OAuth flow required.

Can konfipay trigger a FlowRunner workflow automatically?

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

Start building with konfipay

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us