Banking Provider
One banking provider. One contract.
Connect internal software and selected enterprise clients to normalized account and transaction data without rebuilding each bank integration from scratch.
Access requests are handled over WhatsApp via provider.banka.pro for internal teams and selected enterprise clients.
POST /bank/setup
{
"bankCode": "ziraat",
"username": "demo-user",
"password": "demo-pass"
}
{
"status": true,
"result": [
{
"bankCode": "ziraat",
"customerNo": null,
"accountNo": "TR590001002719909669535001",
"iban": "TR590001002719909669535001",
"accountType": "DIGER",
"accountName": null,
"branchId": "2719",
"branchName": "DÜVENÖNÜ/KAYSERİ ŞUBESİ",
"currency": "TRY",
"balance": "4120605.16",
"blockedBalance": "0.00",
"availableBalance": "4120605.16",
"openingDate": null,
"lastTransactionDate": "2026-03-12 19:47:38",
"raw": { "...": "bank payload" }
}
]
}Capabilities
Normalized setup contract
Every supported bank returns the same account structure, with raw payloads preserved for auditability and bank-specific debugging.
View contract >Stable transaction mapping
Transactions are normalized into a single internal contract with deterministic stamps, consistent direction handling, and bank-aware parsing.
View contract >Private by design
This provider is not a public marketplace API. It is built for internal software and selected enterprise projects with controlled access.
View contract >Bank-specific tolerance
SOAP quirks, inconsistent field names, raw detail cleanup, and fallback logic are handled at the provider layer instead of in client apps.
View contract >Operational fit
The design favors contract consistency, backward compatibility, and dependable integrations over generic public API abstractions.
View contract >Selective enterprise access
The same provider can serve internal products and carefully onboarded partner projects without splitting the integration model.
View contract >At a glance
Bank integrations maintained in one provider layer
Core response families: setup and transactions
Private contract standard for internal and enterprise access
Access Models
Access models for controlled banking integrations.
This provider is used internally and exposed selectively. The operating model is defined per product or client, not as a public self-service API plan.
Use the provider as the shared bank integration layer behind your own internal products and automation flows.
- Shared account and transaction contracts
- Single provider layer across supported banks
- Raw payload preservation for support teams
- Operationally safer rollout path
Expose the same private provider to carefully onboarded enterprise clients that need bank normalization without full custom bank work.
- Private access only
- Per-project onboarding
- Stable request and response contracts
- Backward compatibility awareness
Extend bank-specific mapping and fallback behavior when a project requires deeper operational handling or custom flows.
- Bank-specific normalization updates
- Special parsing and raw-field handling
- Enterprise contract alignment
- Provider-level maintenance approach
Need a private bank integration layer for your internal product or a selected enterprise rollout?
Contact is handled on WhatsApp through provider.banka.pro. Send a message and we will route the request for internal or enterprise access.