What are bank APIs and open banking?
Banks offer their corporate customers corporate API services that let software access account information. On top of that, open banking regulations in Türkiye are building a framework in which account information can be shared through licensed service providers with the customer's explicit consent. Both routes share the same point: account balances and transactions can be read over a secure connection, without logging into online banking.
For companies working with more than one bank, a bank API integration is the fastest way to see the true cash picture. Which route is used depends on the corporate API or open banking service your bank offers and on the contract terms; the connection is always built on the service agreement between you and your bank.
What do we connect?
| Data | Direction | Frequency |
|---|---|---|
| Account balance (TRY and foreign currency) | Bank → middleware → ERP / READERP | Several times a day |
| Account transactions | Bank → middleware → ERP | Several times a day |
| Incoming wire / EFT details | Bank → ERP (account matching suggestion) | When the transaction arrives |
| Internal transfers and outgoing EFTs | Bank → ERP (bank entry) | When the transaction arrives |
| Bank position | Middleware → READERP cash report | On every update |
The default setup is read-only: balances and transactions are read, and no payment or transfer is initiated at the bank. If transactions are to be posted into the ERP as bank entries, that step is designed separately as an ERP integration, and your accounting team's approval step is kept.
Typical scenarios
- Multiple banks, one screen: A company with twelve accounts at five banks sees all its TRY and foreign currency balances in a single table in the morning report. The READERP cash report updates its bank position block with this data.
- Collection matching: The account code or tax number in the description of a dealer's wire transfer is read, and a matching suggestion for the right account appears in the ERP. The accountant approves; manual searching and typing disappear.
- Reconciliation: Bank transactions are compared with the bank entries in the ERP, and unmatched items are listed. We explain our approach to how virtual POS collections show up at the bank in the article virtual POS and bank reconciliation.
How do we work?
- Analysis: Together we list the banks you work with, the number of accounts and the corporate API or open banking option each bank offers you. You handle the contract and application steps with the bank; we stand by you on the technical side.
- Mapping: Account numbers are mapped to the bank account cards in the ERP, along with transaction types and description patterns.
- Test environment: If the bank offers a test environment we start there; otherwise we begin with a controlled, read-only trial.
- Go-live: Banks are switched on one at a time, and in the first days balances are compared with online banking.
- Monitoring: Every call is logged. If the bank side has an outage, the request is queued and retried; the report clearly shows when the balance was last updated.
Security, banking secrecy and KVKK
Bank data is the most sensitive data there is, so we build the setup on the principle of least privilege:
- Only read access is requested for the connection; no payment or transfer permission is defined.
- Where the bank supports it, an IP restriction is applied, so the connection can only be made from a defined server.
- Certificates, keys and passwords are kept in a restricted, encrypted configuration, not in the code, and are never written to logs.
- Account transactions contain the names and descriptions of third parties. This data is protected under banking secrecy and KVKK (Türkiye's Personal Data Protection Law); only authorized users can see it, and access is logged.
KVKK requirements are met in full, at no extra charge. Data is processed on servers in Türkiye.
Related Globya solutions
To talk about your banking setup, call +90 850 432 55 13 or use the contact page. Pricing follows a written proposal after the discovery call. Describe your needs now in 3 minutes
Frequently asked questions
Can payments be made from the bank through this integration?
Our default setup is read-only: balances and transactions are read, and no payment or transfer is initiated. That way the most sensitive permission is never granted.
Does it work with every bank?
It depends on whether your bank offers this service through a corporate API or open banking, and on the contract terms. In the initial analysis we clarify the situation for each bank one by one.
Is the data posted to the ERP automatically?
If you wish, transactions are transferred to the ERP as bank entries, and account matching suggestions are generated for collections. We do not remove the accounting approval step.
How up to date is the balance?
It is updated several times a day, depending on the query frequency the bank allows; the time of the last update is shown in the report.