Solutions
Open banking and bank integration
Ready one-to-one connections with more than twenty banks in Türkiye. Intraday balances and transactions come from open banking services, reconciliation from statement files, and payment instructions as bank-format files.
Ready connections
Connections ready with more than twenty banks
On every ready connection, what comes standard is kept separate from what requires onboarding. In the meeting we mark, item by item, which bank delivers which item and how long it takes.
More bank integrations coming soon…
Delivered as standard
Intraday balances and transactionsVia open banking services and MT942, several times a day.
End-of-day statementMT940 · camt.053 — for reconciliation.
Account and legal entity mappingEach account is mapped to a legal entity and a chart-of-accounts code; nothing enters the totals until the mapping is verified.
Connection healthA dropped connection is never hidden: it is flagged and the affected total is called out.
Requires onboarding
Payment instruction filepain.001 or the bank’s own format; the format is confirmed during onboarding.
Reading loans, guarantees and letters of creditWhich channel delivers limit, blocked and claim data varies by bank.
Corporate file channelSFTP and scheduled job setup.
A bank not on the listThe onboarding timeline is given in writing during the meeting.
Technology
Four channels, one data model
Whichever channel it comes from, data lands in the same model: account, amount, currency, value date, counterparty, source and read time. An entry with an unclear source never enters the totals.
Channel
Technology
Use
Freshness
Open banking services
REST · OAuth 2.0 · mTLS
Intraday balance and transactions (including MT942)
Intraday, minutes
End-of-day statement
MT940 · camt.053 · bank-specific
Reconciliation
End of day
Payment instruction
pain.001 · bank-specific file
Instruction batch generation
On request
Corporate channel
SFTP · scheduled job
Bulk file transfer
Scheduled
1AuthorisationCorporate access and a certificate are set up on the bank side.
2Account mappingEvery account is mapped to a legal entity and a chart-of-accounts code.
3VerificationNo account enters the totals before its mapping is verified.
4MonitoringEvery affected field is flagged when a connection drops.
Security
Connection security and audit trail
mTLS and signed requestsConnections to bank services use mutual certificates.
Key managementCertificates and keys are kept separate per organisation, with expiry tracked.
Role-based permissionsThe user who sets up a connection cannot approve payments; the rule is enforced at the database level.
Audit trailEvery read and every file generated is timestamped on record.
Outage behaviour
What happens when a connection drops
Data is never inventedThe last successful read is used and marked with a hatch pattern.
Impact listEvery field affected by a dropped connection is flagged.
Excluded from the totalA value that cannot be read is never treated as zero; the account is excluded from the total.
BackfillWhen the connection returns, the missing days are backfilled automatically.
Format reference
Supported file and message formats
Format
Standard
Content
Use
camt.053ISO 20022
End-of-day statement
Reconciliation
camt.052ISO 20022
Intraday transactions
Cash position
MT940SWIFT
End-of-day statement
Reconciliation
MT942SWIFT
Intraday transaction notice
Cash position
pain.001ISO 20022
Payment instruction
Instruction batch
CSV / XLSBank-specific
Statement and balance
Onboarding period
Types of integration
Four different integration routes
Open banking servicesREST · OAuth 2.0 · mTLS. Intraday balances and transactions, MT942 dahil.
File transferSFTP or a scheduled job; end-of-day statements and bulk instructions.
REST service (ERP)Reading ledger, invoice, journal and trial balance data.
Read-only databaseFor ERP setups without a REST service.