Trastpay API integration services (UZCARD / HUMO / OpenBanking)

1. SMB accounting sync

An SMB accounting platform pulls daily UZCARD and HUMO transactions for a Trastbank business owner. Through the statement API, transactions land with commission tier, counterparty masked PAN and a stable transaction id, then map cleanly onto OpenBanking-style "transactions" objects in 1C, Bitrix24 or QuickBooks connectors.

2. Microloan dashboard

A consumer-finance dashboard reads online-microloan eligibility responses and repayment schedules from Trastpay. Each response includes decision code, principal, term and instalment plan, which a risk team consumes through a webhook and writes into a credit-bureau-aware ledger to power affordability checks.

3. Cross-border FX reporting

A traveller pays abroad with a Trastbank MasterCard / VISA. The FX module emits conversion events with rate, base and quote currency. We wire these into a treasury system that classifies the spend, applies the customer's home-currency P&L policy and feeds a tax-residency report — fully aligned with OpenFinance reporting fields.

4. Utility-payment automation

A property-management SaaS uses the "My Home" utility endpoints to pull invoice IDs for electricity, gas, water, heating and garbage on a tenant-by-tenant basis, schedules autopay against a Trastpay e-wallet, and pushes confirmation events back into the landlord's ERP.

5. Loyalty & cashback analytics

A retail-tech vendor consumes the 2% cashback ledger plus card-payment metadata to build a customer-value model. The OpenData feed lets the vendor segment Trastbank cardholders by spend category, lift cashback redemption and report uplift back to the merchant network through a clean REST surface.

Deliverables checklist

• API specification in OpenAPI 3.1 / Swagger
• Protocol and auth flow report (OAuth, refresh chain, device binding)
• Runnable source for login, statement, microloan and FX APIs (Python & Node.js)
• Automated tests, mock server and Postman collection
• Compliance guidance covering ZRU-547 personal data and PP-153 financial-sector duties
• Operational runbook: rate limits, retries, webhook replay, idempotency keys

Technical implementation snippets

// 1) Login & device bind (pseudocode)
POST /api/v1/trastpay/auth/login
Content-Type: application/json

{
  "phone": "+998901234567",
  "otp": "482913",
  "device_id": "tp-android-9b2…",
  "client_id": "ofl-partner-001"
}

200 OK
{
  "access_token": "eyJhbGciOi…",
  "refresh_token": "rtk_…",
  "expires_in": 1800,
  "scopes": ["statements:read","microloan:read","fx:read"]
}

// 2) Statement query — UZCARD/HUMO
POST /api/v1/trastpay/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "card_token": "tok_uzcard_8131xx",
  "from": "2026-04-01",
  "to":   "2026-04-30",
  "rail": "UZCARD",
  "include_commission": true,
  "page": 1, "page_size": 100
}

200 OK
{
  "items": [
    {"id":"txn_…","amount":-152000,"currency":"UZS",
     "rail":"UZCARD","commission":380,"posted_at":"2026-04-12T09:14:00+05:00",
     "counterparty_pan":"8600****4421"}
  ],
  "next_page": 2
}

// 3) Microloan webhook (idempotent)
POST https://your-app.example.com/webhooks/trastpay/microloan
X-Trastpay-Signature: v1=…
X-Idempotency-Key: ml_8af0…

{
  "event": "microloan.decision",
  "loan_id": "ml_8af0…",
  "decision": "approved",
  "principal": 12000000,
  "currency": "UZS",
  "term_months": 12,
  "schedule_url": "/api/v1/trastpay/microloan/ml_8af0…/schedule"
}

Regulatory posture

Trastpay sits inside Uzbekistan's regulated financial perimeter. Our integrations follow the Law of the Republic of Uzbekistan No. ZRU-547 "On Personal Data" (2019) and the 2025 Presidential Decree PP-153, which introduces compulsory breach notifications and legal liability for data incidents in the financial sector. Biometric, genetic and telecommunications-related personal data is kept inside Uzbekistan, as required by the amended localization rules.

Operational controls

• Authorization is sourced from the customer (Trastbank account holder) — no scraping of unauthenticated content.
• Tokens are short-lived; refresh and device-binding follow the Central Bank of Uzbekistan's digital banking verification rules effective from April 2026.
• Every API call is logged with consent metadata and request hash for incident response.
• UZCARD and HUMO national payment system rails are addressed under their respective licensing regimes.
• Data minimization: only fields the integration actually needs are surfaced to downstream systems.

About us

OpenFinance Lab is an independent technical studio focused on App protocol analysis, authorized API integration and OpenData / OpenFinance / OpenBanking work. Our team is built from engineers who have shipped at banks, payment processors, KYC vendors and cloud platforms.

• Hands-on experience with UZCARD, HUMO, MasterCard and VISA data flows
• Familiar with Central Asian regulatory expectations and data-localization rules
• Custom Python / Node.js / Go SDKs, test harnesses and Postman collections
• Pipeline coverage from protocol analysis → build → validation → compliance hand-off
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay per call only, no upfront cost

Contact

For quotes or to submit your target app and requirements, open our contact page. Tell us which Trastpay scope you need (statements, microloan, FX, utilities) and your preferred engagement model.

Contact page

Engagement workflow

1. Scope confirmation — which Trastpay flows: statements, microloan, deposit, FX, utilities.
2. Protocol analysis & API design (2–5 business days; longer when device-binding is in scope).
3. Build and internal validation (3–8 business days).
4. Docs, samples and test cases (1–2 business days).
5. First delivery typically lands in 5–15 business days; third-party approvals or sandbox waits may extend the timeline.

FAQ

What inputs do you need to start a Trastpay integration?

How long does a first delivery take?

How do you handle compliance in Uzbekistan?

Which payment networks are covered?