兴趣爱好================================================================================
TRASTPAY API INTEGRATION
Card, Deposit and Microloan Data Access for Uzbekistan's Trustbank App
================================================================================
INTRODUCTION
--------------------
Trastpay is the retail mobile banking app operated by Trustbank PJSB,
a private joint-stock bank in Uzbekistan, built around two card rails
on a single screen — Uzcard and HUMO. Behind its login sits a dense
set of financial records: linked card balances in soum and foreign
currency, card-to-card transfers, soum and FX deposits, microloans up
to 50 million soum, currency conversion history, and utility/budget
payments with cashback.
For fintech teams, lenders, PFM tools and treasury platforms working
in the Uzbek market, this data is highly valuable but locked behind a
consumer login with no formal Open Banking scheme to plug into. A
Trastpay API integration turns that locked-down mobile session into a
documented, queryable interface — built through authorized protocol
analysis of the real, consented app session, never bypassing it.
This article walks through the supported API capabilities, the
primary use cases, and the advantages of integrating Trastpay data
through a structured API layer rather than manual exports.
SUPPORTED API FEATURES
--------------------
[1] Linked-card balance and transaction retrieval
Per-card, per-transaction visibility across Uzcard and HUMO
Soum and foreign-currency transaction history, dated and tagged by rail
[2] Card-to-card transfer data
Transfer records between HUMO, Uzcard and other Uzbek banks
Per-pairing commission detail (HUMO-to-HUMO, HUMO/Uzcard, Uzcard-to-Uzcard)
[3] Deposit account access
Soum and FX deposit balances
Replenishment and partial-withdrawal movement history
[4] Microloan and installment status
Online microloan facilities up to 50 million soum
Lendo and inTend installment plan limits, status and repayment tracking
[5] Currency conversion records
FX exchange history on MasterCard/VISA Trustbank cards
Rate, currency pair and amount per conversion
[6] Bill, budget payment and profile data
Utility ("My Home"), mobile, tax and fine payments with saved templates
Remote identification and e-wallet profile status
USE CASES & APPLICATIONS
--------------------
[1] BOOKKEEPING AND PERSONAL FINANCE MANAGEMENT (PFM)
Sync Uzcard and HUMO statements into one categorized ledger
Automate expense categorization from utility and budget payments
Build multi-currency spend dashboards for soum and FX accounts
[2] LENDING AND CREDIT MONITORING
Read microloan and installment (Lendo, inTend) status in real time
Time follow-on credit offers based on repayment behavior
Score creditworthiness using verified transaction history
[3] TREASURY AND BUSINESS FINANCE PLATFORMS
Consolidate soum and FX deposit balances for Trustbank clients
Track interest accrual and replenishment activity
Feed reconciled balances into ERP or accounting systems
[4] PAYMENTS AND FEE RECONCILIATION DASHBOARDS
Reconcile card-to-card transfer fees against the correct per-rail commission
Tag every transaction by rail (Uzcard or HUMO) at ingest
Detect and flag mispriced or anomalous transfer fees
[5] OPEN BANKING AND ACCOUNT AGGREGATION SERVICES
Aggregate Trastpay alongside Click, Payme, Uzum Bank and other Uzbek apps
Normalize mixed-rail account data into a single unified schema
Support consented, user-authorized data pulls on a recurring schedule
BENEFITS & ADVANTAGES
--------------------
Full mixed-rail visibility — Uzcard and HUMO cards normalized into one consistent record format
Currency-explicit data — soum and FX transactions kept distinct, never collapsed together
Authorized access model — built on the account holder's own consented session, not a workaround
Compliance-aware design — fitted to Uzbekistan's Personal Data Law (ZRU-547) and Bank Secrecy Law
Resilient to biometric login rules — session and consent flow designed around OTP and liveness checks
Documented and testable — OpenAPI specification plus automated tests against real response shapes
Runnable source code delivery — Python or Node.js implementations, not just documentation
SUBSCRIPTION PLANS
--------------------
Two engagement models are available for accessing Trastpay data:
Source-code delivery — a complete build including the runnable
endpoints, OpenAPI/Swagger specification, automated tests and
interface documentation, handed over for a one-time fee starting
at $300, payable after delivery.
Pay-per-call hosted API — call a hosted endpoint and pay only for
what you use, with no upfront cost and no infrastructure to
maintain on your side.
Both paths typically run one to two weeks from kickoff to delivery,
with access and compliance arrangements handled jointly during
onboarding.
CONCLUSION
--------------------
Trastpay holds a uniquely rich dataset for the Uzbek market — mixed
Uzcard/HUMO card activity, deposits, microloans and FX conversion —
all reachable only through an authorized, consent-based integration
approach. Whether the goal is a PFM tool, a lending platform, a
treasury dashboard, or a broader account-aggregation service spanning
Click, Payme, Uzum Bank, Paynet, Oson, Beepul, Apelsin and Anorbank,
a properly documented Trastpay API integration turns scattered mobile
banking data into a structured, query-ready resource.
Teams that need this data should not attempt to reverse-engineer the
session on their own — the right path is authorized protocol
analysis paired with explicit user consent, delivered as clean,
testable endpoints.
--------------------
Learn more and start an integration request at:
https://openbankingstudio.com/trastpay.html
OpenBanking Studio — authorized app interface integration and API
delivery. Trastpay is a third-party app named here for
interoperability and integration purposes only.
================================================================================