Openbank UZ API Integration & OpenBanking Data Services
Uzbekistan's next-generation digital bank — transaction export, Visa-Humo card data, mortgage records & international transfer API integration
Unlock Openbank UZ account data — transactions, balances, mortgages, and card flows — for your platform
Openbank UZ (formerly Smartbank, package ID uz.smartbank) is Uzbekistan's full-service digital bank with co-branded Visa-Humo cards, international wire transfers, digital mortgages, and 24/7 utility payments. In January 2025, Future Open Technology Group acquired 90.2% of Smartbank and officially rebranded it to Open Bank, deepening its integration across the Open ecosystem of cards, marketplace (Open Bazaar), and business banking. The result is a rich data estate — user account records, multi-currency transfers, mortgage term sheets, cashback ledgers, and granular utility payment logs — all highly valuable for fintech integration.
Feature modules available for API integration
Each module corresponds to a distinct data layer inside the Openbank UZ platform. Our protocol analysis and integration work maps each feature to structured REST endpoints with documented request/response schemas, auth flows, and error codes.
Account authentication & session management
We implement the full login and token-refresh lifecycle for Openbank UZ user accounts — including SMS OTP verification, device binding, and session token maintenance. This is the foundation for all downstream data queries and is delivered as a reusable auth module compatible with Python, Node.js, and Go stacks.
Supports both consumer accounts (individual banking) and the Openbank Biznes (uz.smartbank.business) enterprise variant, enabling multi-account orchestration for corporate treasury and payroll use cases.
Transaction history & statement export API
Pull paginated transaction ledgers across all linked Visa and Humo cards, with filtering by date range, amount bracket, merchant category code (MCC), and payment type (QR, NFC, online, ATM withdrawal). Each record returns a normalized JSON object including merchant name, amount in UZS and original currency, balance-after, and transaction reference ID.
Supports export to JSON, CSV, and PDF statement formats — matching the in-app download flow — enabling direct ingestion into accounting software, ERP systems, and analytics platforms without manual re-entry.
Card balance & Visa-Humo card data
Retrieve real-time balances for all cards linked to an account, including the co-branded Visa-Humo card, virtual cards (issued in under one minute via the app), and any additional cards added through home delivery service. The API returns card number (masked), expiry, card scheme, issuing network (Visa or Humo), and current available balance.
This data stream powers spending-limit enforcement, real-time alert systems, and multi-card consolidation views in PFM and expense management applications targeting users in Uzbekistan's growing digital banking cohort.
International transfer logs & FX data
Openbank UZ enables users to send money abroad via international wire transfers — quickly and securely. Our integration maps the transfer initiation and confirmation flows, extracting structured records including destination country, correspondent bank, SWIFT code, original and converted amounts, FX rate applied, fee charged, and settlement status (pending / cleared / failed).
This makes Openbank UZ a key data source for businesses managing cross-border payroll, remittance reconciliation, or multi-currency cash-flow reporting across Central Asia.
Digital mortgage & installment plan data
Openbank UZ offers fully digital mortgage applications with terms from 2 to 10 years — all steps handled online with no branch visits. Through protocol analysis we extract mortgage application status, approved loan amount, repayment schedule (principal + interest breakdown per period), next due date, and outstanding balance. This data is critical for credit bureaus, wealth management apps, and risk engines.
Open Bazaar installment plans (interest-free, up to 50 million UZS) add a secondary credit data layer: merchant name, item category, installment tenor, monthly payment, and payoff date — covering the buy-now-pay-later analytics use case prevalent in Uzbekistan's rapidly expanding e-commerce segment.
Utility payments & cashback ledger
Users pay utility bills and services 24/7 through Openbank UZ, earning up to 1.5% cashback on qualifying transactions. Our integration captures per-payment records (provider name, service category, amount, payment date, reference number) alongside corresponding cashback credit events — enabling expense categorization, budget tracking, and loyalty analytics for household finance applications.
With QR payment metadata also available (merchant ID, location, amount, time), the combined utility + QR stream provides a near-complete picture of a user's day-to-day spending behavior in the Uzbekistan market.
Data available for integration (OpenData inventory)
The table below catalogues the structured data types accessible through Openbank UZ protocol analysis and authorized API integration. Each row identifies the source screen or feature within the app, the granularity at which data can be retrieved, and the primary downstream use case.
Typical integration scenarios
The following end-to-end scenarios illustrate how businesses actually use Openbank UZ data exports and API integration to drive operational value. Each scenario maps specific data types to a concrete business outcome and the OpenData or OpenFinance pattern it instantiates.
Scenario 1 — Personal Finance Management (PFM) app with multi-account aggregation
Business context: A Uzbekistan-based PFM startup wants to show users a unified view of spending, balances, and upcoming bill payments across all their bank accounts, including Openbank UZ.
Data involved: Card transaction history (Visa + Humo), real-time balances, utility payment records, and cashback ledger — all pulled via the Openbank UZ statement API on a nightly or on-demand basis.
OpenData mapping: This follows the Account Information Service (AIS) pattern from open banking frameworks worldwide. The user grants consent once; the PFM app queries /accounts/{id}/transactions and /accounts/{id}/balances, normalizes the data, and serves it in the aggregation UI. The cashback ledger doubles as a loyalty data feed for personalized offer targeting.
Scenario 2 — Corporate treasury reconciling employee expense cards
Business context: An Uzbekistani company issues Openbank Biznes cards (uz.smartbank.business) to employees and needs to reconcile daily card spend against internal purchase orders in their ERP (e.g., 1C, SAP) without manual export.
Data involved: Per-card transaction records (MCC, merchant, amount in UZS), card holder metadata, and QR payment events with merchant IDs.
OpenData mapping: A scheduled integration job calls the transaction export API for each business card, maps MCC codes to internal cost categories, and posts normalized records to the ERP via webhook. Delta-sync (last-seen transaction ID) keeps the payload lean and avoids duplicate entries during reconciliation runs.
Scenario 3 — Alternative credit scoring using mortgage and installment repayment data
Business context: A microfinance institution or credit bureau in Uzbekistan wants to build an alternative credit score for thin-file applicants who hold Openbank UZ mortgages or Open Bazaar installment plans.
Data involved: Mortgage repayment schedule adherence (on-time vs. late payments), installment plan completion rates, and utility payment consistency — all sourced from Openbank UZ with user consent.
OpenData mapping: This matches the Open Finance credit data model: structured repayment records are exported via the mortgage API (/loans/{id}/schedule), enriched with cashback rate data as a positive behavioral signal, and fed into a scoring model. No traditional credit history required.
Scenario 4 — Cross-border remittance monitoring and FX compliance reporting
Business context: A remittance service or compliance team needs to monitor international wire transfers sent through Openbank UZ, cross-referencing destination countries, correspondent banks, and amounts against sanctions lists and reporting thresholds.
Data involved: International transfer log API — per-transfer records including SWIFT reference, beneficiary country, correspondent bank BIC, amount in original and UZS, FX rate, and settlement status.
OpenData mapping: The integration pulls the transfer stream via /transfers/international?status=cleared&from=2025-01-01, runs each record through a sanctions screening micro-service, and flags transactions above CBU reporting thresholds for manual review — automating a compliance workflow that previously required daily manual exports.
Scenario 5 — Real-time spending alerts and budget enforcement for consumer fintech
Business context: A consumer budgeting app wants to push real-time SMS or push notifications when an Openbank UZ card transaction exceeds a user-defined category budget (e.g., dining, utilities).
Data involved: Transaction webhook stream — per-authorization event with merchant category code (MCC), amount, and card identifier — combined with the cashback ledger to compute net spend after rewards.
OpenData mapping: Our integration provisions a server-sent event (SSE) or polling adapter that monitors the Openbank UZ session for new transaction events, normalizes the MCC into a spending category, checks against a user's stored budget, and triggers the alert via the app's notification service — achieving sub-minute latency from card swipe to push notification.
Technical implementation — API snippets
The following pseudocode samples illustrate the request/response shape, authentication method, and error-handling approach for three core Openbank UZ integration endpoints. All delivered code is runnable and fully documented.
1. Account login & session token acquisition
// Step 1: Initiate login, trigger OTP POST /api/v2/auth/login Content-Type: application/json { "phone": "+998901234567", "device_id": "<DEVICE_FINGERPRINT>" } // Response: OTP sent to registered phone { "session_id": "sess_abc123", "otp_ref": "otp_xyz789", "expires_in": 120 } // Step 2: Confirm OTP, obtain access token POST /api/v2/auth/verify { "session_id": "sess_abc123", "otp": "482910" } // Response { "access_token": "eyJ...", "refresh_token": "rft...", "expires_in": 3600, "user_id": "u_0041882" }
2. Transaction history query with pagination
// Fetch card transactions (paginated) GET /api/v2/accounts/{account_id}/transactions Authorization: Bearer <ACCESS_TOKEN> X-Device-Id: <DEVICE_FINGERPRINT> Query params: from_date=2025-01-01 to_date=2025-03-31 card_id=card_visa_humo_001 page=1&page_size=50 // Response { "total": 312, "page": 1, "items": [ { "txn_id": "txn_9981", "date": "2025-03-20T14:32:00+05", "merchant": "Korzinka", "mcc": 5411, "amount_uzs": 85000, "original_currency": "UZS", "balance_after": 2345000, "type": "purchase", "cashback": 1275 } ] } // Error: token expired → refresh and retry HTTP 401 { "code": "TOKEN_EXPIRED", "refresh_with": "POST /auth/token/refresh" }
3. International transfer log & mortgage schedule
// International transfer history GET /api/v2/transfers/international Authorization: Bearer <ACCESS_TOKEN> ?status=cleared&from=2025-01-01 // Response item { "transfer_id": "wt_0055", "date": "2025-02-10", "beneficiary_country": "RU", "swift_ref": "SABRRUMM", "amount_original": 500.00, "currency": "USD", "amount_uzs": 6350000, "fx_rate": 12700, "fee_uzs": 25000, "status": "cleared" } // Mortgage repayment schedule GET /api/v2/loans/{loan_id}/schedule { "loan_id": "mtg_0012", "term_years": 7, "monthly_payment_uzs": 1850000, "next_due": "2025-04-15", "outstanding_uzs": 128500000, "payments": [ { "period": 1, "principal": 1200000, "interest": 650000, "status": "paid" } ] }
Compliance & privacy framework
Uzbekistan Open Banking Act (2026) & CBU regulations
By 1 September 2026, Uzbekistan will formally introduce an Open Banking legal framework mandating secure data-sharing between banks, payment institutions, and licensed fintech providers — positioning Openbank UZ at the centre of a regulated API ecosystem. Our integration work anticipates this transition: all protocol analysis is performed under explicit user authorization, and data access is scoped to the minimum necessary for the stated integration purpose.
Openbank UZ operates as a licensed bank under the Central Bank of the Republic of Uzbekistan (CBU), which sets capital adequacy, AML, and consumer data protection requirements. We align our implementations with CBU Circular No. 18/1 on remote banking services and the personal data protection provisions of the Law of the Republic of Uzbekistan on Personal Data (2019, amended 2022).
UZCARD / HUMO infrastructure & data minimization
Both UZCARD and HUMO — the two national payment rails that Openbank UZ cards run on — are designed as open platforms with structured API access, enabling fintech integration in a manner that is architecturally consistent with PSD2-style open banking norms established in the European Union. Our deliverables include consent-capture flows and token-scoping documentation to ensure integrations remain within the bounds of the user's explicit authorization.
We apply data-minimization principles throughout: only fields required for the stated use case are extracted and stored; PAN and CVV data is never persisted in integration logs; and all access tokens are stored encrypted using AES-256. An optional audit-log module (delivered as part of the compliance package) records every API call with timestamp, endpoint, and user consent reference for regulatory review.
Data flow & integration architecture
A typical Openbank UZ integration pipeline follows four stages, keeping data sovereignty and latency both in check:
- Client App layer: Openbank UZ mobile app (
uz.smartbank) on Android or iOS authenticates the user; our auth module captures the session token via the SMS-OTP flow and stores it in an encrypted vault on the integration server. - Ingestion / API gateway: A scheduled job (or event-driven webhook adapter) calls the Openbank UZ REST endpoints for transactions, balances, transfers, and loans. Delta-sync ensures only new or updated records are fetched on each run, reducing bandwidth and avoiding duplicate processing.
- Normalization & storage: Raw API responses are normalized to a common schema (ISO 4217 currency codes, ISO 8601 timestamps, MCC-to-category mapping), then written to a time-series store or relational database. Sensitive fields (card number, IBAN) are hashed or masked before storage.
- Analytics / API output: The normalized dataset is served via a client-facing REST or GraphQL API, or fed directly into BI tools (Metabase, Grafana), ERP systems, or credit scoring engines. Webhooks push real-time transaction events to downstream consumers without polling overhead.
Full pipeline diagram (Mermaid/Lucidchart source) and a Docker Compose dev stack are included in the source code deliverable.
Market positioning & user profile
Openbank UZ targets Uzbekistan's rapidly digitizing consumer and SME segment — a market where the number of licensed fintech companies grew from 24 in 2018 to 103 in 2025 (Central Bank data), and where the Fast Payment System processed over $10.2 billion in a single month (July 2025). The app's primary users are digitally active individuals aged 20–45 in Tashkent and other urban centres who want a single platform for everyday payments, international transfers, and credit products — without visiting a branch.
Since the January 2025 acquisition by Future Open Technology Group, Openbank UZ has been embedded in a broader ecosystem that includes the Open Bazaar marketplace and the Openbank Biznes platform for SMEs. This dual B2C and B2B footprint means the integration data estate spans both consumer transaction flows and business card expense records — making it uniquely valuable for fintech builders serving both segments simultaneously.
Platform distribution is primarily Android (dominant in the CIS region; the uz.smartbank package on Google Play), with full iOS parity via the App Store (id6446754221). International clients and diaspora communities sending remittances into Uzbekistan are a growing secondary user group, driven by the app's cross-border transfer feature.
App screenshots
Click any thumbnail to view a larger version.
Similar apps & Uzbekistan integration landscape
Openbank UZ operates alongside a vibrant ecosystem of Uzbekistani fintech apps. Businesses that need unified data access across platforms — or that are evaluating their options — will find that Openbank UZ's data types overlap meaningfully with the following apps. Each represents a distinct integration opportunity within the same market.
Payme is Uzbekistan's most widely installed finance app, facilitating peer-to-peer transfers and online payments across Humo and UzCard rails. Users who run both Payme and Openbank UZ accounts often need unified transaction exports and balance aggregation across both platforms — a common multi-bank PFM integration scenario.
Uzum is Uzbekistan's dominant super-app combining marketplace, food delivery, and banking services. Its $70M funding round in 2025 underscores the scale of the opportunity. Businesses building on the Uzbekistan ecosystem frequently need to reconcile Uzum payment flows alongside Openbank UZ card transactions to get a complete picture of user spending.
Click launched Uzbekistan's first USSD payments and peer-to-peer transfer service and remains a foundational payment layer for many Uzbekistani users. Integrating Click transaction data alongside Openbank UZ mortgage and installment records provides a comprehensive credit and spending profile for alternative lending platforms.
MyUzcard is the official mobile application of the United Republican Processing Center (UZCARD brand), giving access to the national card network that underpins Openbank UZ's Humo co-branded card. Developers who integrate MyUzcard account data often extend the same pipeline to Openbank UZ to cover the Visa-side transaction flows.
Uzum Bank, the banking arm of the Uzum super-app ecosystem, holds structured account and loan data comparable to Openbank UZ. Businesses building credit scoring or PFM tools for the Uzbekistan market often need to integrate both Uzum Bank and Openbank UZ to cover their user base fully.
Paynet is one of Uzbekistan's oldest payment companies, with a large network of physical kiosks and digital channels for utility and service payments. Its payment records are a complementary data source to Openbank UZ's utility payment API — together they cover the full breadth of household bill payment behaviors in the country.
Beepul is the payment app of Beeline Uzbekistan (VEON group), offering telecom-anchored mobile payments. Users with both Beepul and Openbank UZ accounts represent a cross-platform integration opportunity for telecom-fintech convergence use cases, such as data-plan purchase financing or airtime-backed microloans.
Upay is a smaller but established payment application in the Uzbekistan market. Its presence in the ecosystem is relevant for developers building comprehensive payment aggregation layers, since some user segments rely on Upay for specific merchant categories not covered by larger platforms like Openbank UZ or Payme.
What we deliver
Deliverables checklist
- OpenAPI / Swagger specification for all integrated Openbank UZ endpoints
- Protocol & auth flow report (SMS-OTP, device binding, token lifecycle)
- Runnable source code in Python and/or Node.js (login, statement, transfer, mortgage APIs)
- Normalized data models and schema documentation (JSON Schema / Pydantic)
- Automated test suite with mock fixtures for CI/CD integration
- Compliance guidance: CBU data rules, Personal Data Law (UZ 2022), UZCARD / HUMO constraints
- Integration guide and onboarding documentation (Markdown + Postman collection)
Engagement models
Source code delivery — from $300
We deliver runnable API source code, full documentation, and a test suite. You own the code. Payment after delivery upon your satisfaction — no upfront risk.
Pay-per-call API billing
Access our hosted Openbank UZ integration endpoints and pay only for the calls you make. No upfront fee, no infrastructure overhead. Ideal for teams that want to ship fast and scale usage-based.
Both models include the same underlying integration quality and compliance documentation. Choose source code for full control; choose pay-per-call for zero infrastructure commitment.
About our studio
We are an independent technical service studio specializing in app interface integration and authorized API integration for global clients. Our team brings deep hands-on experience across mobile application engineering and fintech — covering protocol analysis, interface refactoring, Open Data integration, and third-party API implementation.
We have delivered production-grade integrations for banking, e-commerce, travel, and payments apps across Southeast Asia, Central Asia, South Asia, and Europe. Our Uzbekistan coverage includes familiarity with UZCARD, HUMO, CBU regulatory norms, and the emerging Open Banking framework scheduled for 2026.
- Android and iOS protocol analysis — both platforms, all major Uzbekistani fintech apps
- Custom Python / Node.js / Go SDKs with full test harnesses
- Full pipeline: protocol analysis → build → validation → compliance review
- NDAs available; all work under explicit user authorization and data-minimization principles
- Source code delivery from $300 — pay after delivery upon satisfaction
- Pay-per-call API access — usage-based, no upfront commitment
Contact us
To submit your Openbank UZ integration requirements or get a quote, use our contact page. Provide the target app name (Openbank UZ), your specific data needs (e.g. transaction history, mortgage export, international transfer logs), and any existing backend credentials or sandbox access — and we will scope the engagement within one business day.
Typical first response: within 24 hours on business days. Delivery of first API drop: 5–12 business days depending on integration scope.
Engagement workflow
- Scope confirmation — Agree on which Openbank UZ data types and endpoints are required (transactions, transfers, mortgage, etc.) and desired output format (JSON, CSV, webhook).
- Protocol analysis & API design — Reverse-engineer the app communication layer, document auth flows, and draft the integration spec. Typically 2–4 business days.
- Build & internal validation — Implement the integration modules, write unit and integration tests, validate against live data. Typically 3–7 business days.
- Documentation & handover — Produce OpenAPI spec, Postman collection, integration guide, and compliance notes. 1–2 business days.
- Delivery & support — First delivery typically within 5–12 business days. We provide a 30-day support window for bug fixes and clarifications post-delivery.
FAQ
What do you need from me?
Do you support both Android and iOS?
uz.smartbank on Google Play) and iOS (App Store ID 6446754221). We support protocol analysis and integration for both platforms and deliver a single unified API layer.How do you handle the Uzbekistan data regulations?
App overview — Openbank UZ (appendix)
Openbank UZ (formerly Smartbank, package ID uz.smartbank) is a full-service digital bank operating in Uzbekistan under the Central Bank of the Republic of Uzbekistan. In January 2025, Future Open Technology Group acquired 90.2% of Smartbank for 451 billion soums and rebranded the platform to Open Bank, integrating it into a wider ecosystem that includes the Open Bazaar marketplace and the Openbank Biznes business banking platform.
- Co-branded Visa-Humo card with free home delivery and instant virtual card issuance (under one minute)
- International wire transfers — send money abroad quickly and securely via SWIFT / correspondent banking
- Digital mortgages — fully online application, terms from 2 to 10 years, no branch visits required
- Open Bazaar installment plans — up to 50 million UZS, interest-free, with no hidden fees
- Utility and bill payments available 24/7 with up to 1.5% cashback on qualifying transactions
- QR code payments for goods and services; continuous security and data protection updates
- Free transfers between Humo and UzCard cards with no cross-network fee
- Available on Android (Google Play) and iOS (App Store) — full feature parity across platforms
This appendix describes the original app for reference. The integration services described on this page are provided by our studio independently and are not affiliated with or endorsed by Open Bank / Smart Bank JSC or Future Open Technology Group.