Bring Uzum Business | Kapitalbank corporate accounts into your stack
Uzum Business by JSCB Kapitalbank is a mobile bank used by Uzbek legal entities to manage UZS and FX accounts, sign payments, run payroll, and review statements. We expose those same actions as machine-readable APIs so your ERP, accounting platform, treasury dashboard, or compliance pipeline can read balances, push payment batches, and stream transaction events without screen scraping the mobile UI.
Data available for integration
The Uzum Business | Kapitalbank app is, in practice, a structured data front-end on top of corporate ledger, payments and FX systems. The table below maps the data surfaces we typically expose in an integration project, the in-app source screen, granularity, and the most common downstream use case.
| Data type | In-app source | Granularity | Typical use |
|---|---|---|---|
| Corporate account list & balances | "All accounts" / "Cards" section | Per account, per currency, current available balance | Treasury dashboards, daily cash position, multi-entity rollups |
| Transaction history (incoming & outgoing) | "History" section, per account | Per transaction: date, counterparty, INN/MFO, amount, currency, narrative, status | Bookkeeping reconciliation, ERP posting, anti-fraud screening |
| Statements | Statement generation per account / range | Date range, sortable, exportable to PDF/Excel | Audit packages, tax reporting, lender due diligence |
| Payment templates & created payments | Payment forms & templates | Per template: counterparty, purpose, fixed/variable fields | Recurring vendor payments, payroll, government taxes |
| Payroll runs | Salary payment workflow | Per employee row: amount, account, status | HR/payroll automation, salary file ingestion |
| FX and SWIFT operations | Currency exchange & SWIFT transfer modules | Per deal: currency pair, rate, contract reference | Cross-border settlement, currency-contract tracking |
| Push notifications | Account event notifications | Per event: type, amount, timestamp | Real-time accounting triggers, fraud alerts |
Typical integration scenarios
1. ERP & 1C accounting reconciliation
Many Uzbek SMEs run 1C, SAP B1 or local ERP suites. Our integration polls the statement endpoint nightly per corporate account, normalizes counterparty INN, MFO and purpose codes, and posts journal entries back to the ERP via its inbound API. Maps directly to OpenBanking account information services.
2. Treasury dashboard for multi-entity holdings
Holding companies that operate multiple legal entities each with their own Uzum Business profile use our APIs to roll up balances and pending payments into a single treasury cockpit. The signing step still happens inside the licensed app to preserve the user's signing key, while read-only data and payment preparation run outside.
3. Payroll automation from HRIS
An HR system computes monthly salaries and pushes a payroll batch through our API. The batch is created as a Uzum Business payment template, returned for approval inside the app, and the same-day credit confirmations are pushed back as webhooks so HR can mark salary slips as paid automatically.
4. Cross-border SWIFT & currency-contract tracking
Importers and exporters must match each SWIFT outbound or inbound to a specific currency contract. We expose the SWIFT and currency-contract views as a single OpenFinance resource so trade-finance software can check contract utilization and FX exposure in real time.
5. Compliance evidence pack for audits
For lender due diligence or KPMG/Big-4 audits, we package a date-bounded export of statements, payment requests in Card File 1 and Card File 2, and signed payments. Output is a deterministic ZIP with PDF statements, JSON ledger and a manifest hash so auditors can verify completeness.
Technical implementation
Authorization (OAuth-style session bootstrap)
POST /api/v1/uzum-business/auth/login
Content-Type: application/json
{
"username": "uz_corp_user",
"password": "********",
"device_fingerprint": "f4c1...e2",
"second_factor": {
"type": "access_code",
"value": "******"
}
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rt_8c1f...",
"expires_in": 1800,
"signing_capabilities": ["payment.sign", "payroll.sign", "swift.sign"]
}
Statement export by account & date range
POST /api/v1/uzum-business/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"account_id": "20208000900123456789",
"currency": "UZS",
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"format": "json"
}
200 OK
{
"account_id": "20208000900123456789",
"opening_balance": 152340000,
"closing_balance": 178902150,
"currency": "UZS",
"items": [
{
"tx_id": "TX-2026-04-12-0011",
"posted_at": "2026-04-12T10:14:33+05:00",
"direction": "credit",
"amount": 12500000,
"counterparty": {
"name": "LLC Trade Partner",
"inn": "302345678",
"mfo": "00842"
},
"narrative": "Invoice 2026-INV-118"
}
]
}
Webhook: incoming payment notification
POST https://your-app.example.com/uzum/webhook
X-Signature: hmac-sha256=...
{
"event": "transaction.incoming",
"account_id": "20208000900123456789",
"tx_id": "TX-2026-04-12-0011",
"amount": 12500000,
"currency": "UZS",
"counterparty_inn": "302345678",
"received_at": "2026-04-12T10:14:33+05:00"
}
// expected response
200 OK
{ "status": "received" }
Compliance & privacy
Regulatory alignment
Every Uzum Business | Kapitalbank integration we ship operates under written customer authorization or documented public APIs and follows guidance from the Central Bank of the Republic of Uzbekistan, which has set a national open-banking rollout target of September 2026. For EU- and UK-headquartered clients we layer GDPR-aligned data minimization on top, and for trade-finance scenarios we follow SWIFT message standards. Our delivery never bypasses the customer's signing key — final payment and SWIFT signatures still happen inside the licensed Uzum Business app or web Internet Bank.
Privacy & data handling
- Per-tenant token vault; no shared credentials between integrations
- PII minimization — only INN, MFO, account number and amount are stored; counterparty PII is hashed unless the use case requires it
- Audit log of every API call, signing event and webhook delivery
- Configurable data residency: Uzbekistan, EU, or hybrid
- Optional NDA, signed source-code escrow, and right-to-be-forgotten endpoint
Data flow & architecture
A typical deployment looks like this: Uzum Business mobile / Internet Bank → OpenFinance Lab API gateway (auth, rate limiting, webhook signing) → Normalized event bus (Kafka, NATS, or AWS EventBridge) → Storage tier (Postgres for ledger snapshots, S3-compatible object store for PDF statements) → Consumers (your ERP, BI dashboard, fraud system, or downstream API).
Read-only flows (balance, statement, history) run on a 1–5 minute polling schedule plus push notifications when available. Write flows (payment creation, payroll batch upload) are queued and replayed idempotently. The signing step is always interactive — performed by the authorized corporate user in the official app — and the integration only orchestrates the surrounding data.
Market positioning & user profile
Uzum Business | Kapitalbank is aimed at legal entities (B2B) banking with JSCB Kapitalbank in Uzbekistan — small and medium businesses, holding companies, and corporate departments that need to sign payments outside the office. The parent Uzum ecosystem reported more than 17 million monthly active users in August 2025 and a $2.3B valuation in March 2026, making Kapitalbank one of the most active corporate banks in the country. Primary regions are Uzbekistan and the wider Central Asia corridor (CIS, UAE, Turkey trade flows). Both Android and iOS are supported, with the mobile app fully synchronized with the desktop Internet Bank, so an integration built for one surface immediately reflects activity from the other.
Screenshots
Click any thumbnail to view a larger version. Screenshots are provided by the publisher on Google Play.
Similar apps & integration landscape
Teams running on Uzum Business | Kapitalbank rarely operate in isolation. Below is a non-ranked map of related Uzbek and Central Asian banking and payment apps. We also build OpenBanking-style adapters for them, which is useful when finance teams need a single, normalized API across multiple banks.
What we deliver
Deliverables checklist
- OpenAPI / Swagger specification for every exposed endpoint
- Protocol & auth flow report (token lifecycle, signing surface)
- Runnable source code in Python or Node.js (FastAPI / Express)
- Docker Compose stack and integration tests against a sandbox tenant
- Webhook simulator and replay tool for incoming-payment events
- Compliance memo referencing Central Bank of Uzbekistan guidance
Engagement workflow
- Scope confirmation: which Uzum Business modules (login, statements, payments, payroll, SWIFT)
- Authorized protocol analysis & API design (2–5 business days)
- Build, internal validation, and signed test runs (3–8 business days)
- Documentation, sample code and integration tests (1–2 business days)
- Handover, post-delivery support window, and optional managed-API mode
About OpenFinance Lab
We are an independent technical studio focused on App interface integration and authorized API integration for fintech, e-commerce and travel. Our engineers come from banks, payment gateways, mobile reverse-engineering teams and cloud platforms across Central Asia, the EU and South Asia. We have shipped corporate banking adapters, statement-export pipelines, and SWIFT bridges for clients ranging from Big-4 audit teams to mid-market ERPs.
- Two engagement models: Source-code delivery from $300 (pay-after-satisfaction) or pay-per-call hosted API (no upfront fee)
- Android and iOS coverage, both consumer and corporate banking
- Familiar with Uzbekistan, EU, GCC and South Asian regulatory profiles
- Optional NDA and source-code escrow on every engagement
Contact
To request a quote or share your Uzum Business | Kapitalbank integration scope, open our contact page below. We respond within one business day.
FAQ
What do you need from me to start a Uzum Business | Kapitalbank integration?
How long does delivery take for a Kapitalbank corporate API drop?
How do you handle compliance with the Central Bank of Uzbekistan?
Can the integration cover SWIFT and currency operations?
📱 Original app overview (appendix)
Uzum Business | Kapitalbank (package uz.kapitalbank.mobile24) is the mobile bank for legal entities of JSCB Kapitalbank, one of the largest commercial banks in Uzbekistan. The app lets corporate users manage company finances on the go: balances and movements across all accounts, payments to other Uzbek banks and government agencies, currency exchange, SWIFT transfers, payroll runs, payment requests in Card Files 1 and 2, planned (date-scheduled) payments, push notifications, and one-tap sharing of account/card details.
- Easy and fast login — username/password once, then access code, fingerprint or face recognition.
- Quick payment creation — convenient forms and reusable templates; bulk-sign one or all available payments.
- Currency operations — SWIFT transfers, currency exchange, view of currency contracts.
- All accounts in one place — current accounts and cards in a single section; statements per account.
- Salary payments — create payroll, fill amounts, sign — same-day credit to employees.
- Mobile + Internet Bank synchronized — start a payment on the web, finish signing in the app, or vice versa.
- Other features — planned payments, payment requests, full transaction history search, push notifications.
Listings: Google Play · App Store · publisher page on kapitalbank.uz.