Pull uPay.net top-up history, payment receipts and operator data into your stack — under your authorization
uPay.net (package net.uzpaynet) is a New York-based cross-border recharge service founded in 2016 with more than 100,000 users worldwide, built specifically to let the diaspora top up mobile, internet and utility accounts in Uzbekistan and Tajikistan. We deliver authorized APIs that surface the structured financial data already living inside the app: send-money intents, recharge receipts, saved beneficiary numbers, supported operators and per-transaction status — so your CRM, accounting, anti-fraud or BI tools see the same picture as the user does.
Data available for integration (OpenData inventory)
The matrix below maps the structured records uPay.net already collects to the integration surface we expose. Each row is derived from observable in-app screens (recharge form, history list, receipt page, saved numbers, payment methods) plus the public service description, and each one becomes a documented endpoint or webhook in the delivered SDK.
| Data type | Source (in-app screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Recharge transaction | "History" screen / receipt detail | Per-transaction: amount, FX, operator, MSISDN, status, timestamp | Reconciliation, accounting export, anti-fraud scoring |
| Saved beneficiaries | "Favorite numbers" list | MSISDN + nickname + last operator | Address-book sync, repeat-customer marketing |
| Payment method on file | "Cards" / PayPal binding | Brand, last4, BIN country, expiry, status | PCI-safe billing, churn detection, dunning |
| Operator price catalogue | Recharge form (country → operator → amount) | Per-SKU: min/max, retail USD, local currency total | Price comparison, partner pricing pages |
| FX rate snapshot | Receipt + checkout page | USD↔UZS, USD↔TJS at order time | Treasury reporting, margin analysis |
| Utility & ISP bill payments | Utility / Internet provider flows | Provider, account number masked, amount, period | Household-spending categorization, BNPL eligibility |
| User profile & KYC flags | Profile screen | Email, residency country, verification level | Compliance, sanctions screening, segmentation |
Typical integration scenarios
1. Diaspora-fintech super-app embedding
A US- or UAE-based remittance fintech serving Central Asian customers wants to add "top up a phone in Uzbekistan" alongside its money-transfer flow. We expose a POST /recharge endpoint mapped to uPay.net's send-money request, plus a GET /recharges/:id status poller and a webhook for completion. The OpenFinance angle: the user authorizes a single account-aggregation token covering both remittance ledger and recharge ledger.
2. Accounting & expense reconciliation
Small Uzbek-American businesses use uPay.net to recharge employee phones back home. We pull the full statement via GET /transactions?from=&to=, classify each row by operator and beneficiary, and push a CSV/Excel feed to QuickBooks or Xero through their bank-feed APIs — turning recharge spend into categorized OPEX.
3. Anti-fraud & sanctions screening
Compliance teams need to score recharge flows against velocity rules and OFAC/UN sanctions lists. The exposed /transactions stream plus payment-method metadata feeds a real-time scoring service; high-risk recharges (e.g. unusual MSISDN spread) trigger holds via the same webhook channel. This mirrors the OpenFinance "transaction enrichment" pattern adapted to remittance.
4. Operator-side reporting & settlement
An MNO partner (Beeline, Ucell, Mobiuz, Humans) wants a daily roll-up of inbound top-ups it received via uPay.net. We aggregate operator_id, amount_local, fx_rate and settlement_window, then deliver a signed JSON Lines file to S3 — usable as the source-of-truth for inter-carrier settlement and revenue assurance.
5. Customer-facing self-service & receipts
Issue PDF and JSON receipts on demand for end users (e.g. for tax authorities or expense tools), with the exact FX, fees and operator confirmation reference. Building this on top of the statement API removes the need to scrape email confirmations or screenshot the in-app history page.
Technical implementation
1) Login & session bridge
POST /api/v1/upaynet/auth/login
Content-Type: application/json
{
"email": "user@example.com",
"password_token": "<short-lived auth blob from client>",
"device_id": "9f2e-...-c1",
"client_locale": "en_US"
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rt_8a1c...",
"expires_in": 3600,
"user": {
"id": "usr_18429",
"country": "US",
"kyc_level": "L1"
}
}
2) Statement / recharge history
GET /api/v1/upaynet/transactions
?from=2026-04-01&to=2026-04-30&type=recharge
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"page": 1, "total": 47,
"items": [{
"id":"tx_92f1",
"destination_msisdn":"+99890XXXXXXX",
"operator":"ucell",
"country":"UZ",
"amount_usd":"10.00",
"amount_local":"125400.00",
"currency_local":"UZS",
"fx_rate":"12540.00",
"payment_method":"visa_***4242",
"status":"delivered",
"completed_at":"2026-04-22T17:08:14Z"
}]
}
3) Webhook: top-up completion
POST https://your.app/webhooks/upaynet
X-OFL-Signature: t=1714999999,v1=8e2c9a...
Content-Type: application/json
{
"event":"recharge.delivered",
"tx_id":"tx_92f1",
"operator":"mobiuz",
"country":"UZ",
"amount_usd":"5.00",
"amount_local":"62700.00",
"currency_local":"UZS",
"operator_ref":"OP-7782341",
"delivered_at":"2026-04-22T17:08:16Z"
}
# Verify HMAC-SHA256 over the raw body using your shared secret
# before trusting the payload. Reject events older than 5 minutes
# to defeat replay attacks.
Compliance & privacy
uPay.net handles cross-border remittance-style top-ups originated mostly in the United States and delivered into Uzbekistan and Tajikistan, so the integration touches three regulatory domains. On the issuing side, card-data flows align with PCI DSS v4.0 — the integration only exchanges tokens and last4 digits, never raw PANs. On the receiving side, Uzbekistan's Personal Data Law (No. ЗРУ-547) requires that personal data of Uzbek residents be stored on servers physically located in Uzbekistan; we provide a data-residency switch so resident records can be partitioned. For EU-based operators of partner apps, GDPR data-minimization and DSR endpoints are exposed by default.
We document every consent event, ship a default 30-day retention for raw recharge logs (configurable), and never use scraping techniques outside an authorized agreement. NDAs are standard, and our protocol-analysis reports redact any third-party material that is not the customer's to share.
Typical modules
- OAuth-style login & refresh-token rotation
- Transaction / statement export with paging
- Operator catalogue & price feed (UZS, TJS)
- Card & PayPal payment-method introspection
- Webhook stream: recharge.created / .delivered / .failed / .refunded
- Saved-beneficiaries CRUD
- Audit log + consent ledger for compliance review
Data flow & reference architecture
The pipeline is intentionally minimal so it can be audited end to end:
- Client App / Mobile SDK — captures the user's authorization and forwards intents (login, recharge, statement query).
- OpenFinance Lab Gateway — terminates TLS 1.3, validates HMAC-signed requests, applies rate limiting and translates them into the uPay.net protocol shape.
- Normalization & Storage Layer — converts upstream responses into the documented JSON schema, stores recharge events in a partitioned Postgres ledger, and emits a Kafka stream of
recharge.*events. - API / Webhook Output — partner apps consume either the REST endpoints (pull) or the signed webhook stream (push). A daily JSON Lines snapshot is written to S3-compatible storage for batch BI use.
Every node enforces append-only audit logging and is deployable in either a US or Uzbekistan region to meet residency rules.
Market positioning & user profile
uPay.net's core user is the Central Asian diaspora — Uzbek and Tajik nationals living in the United States, the Gulf, Russia, Turkey or the EU who need to top up family members' phone, internet or utility accounts back home. The company was founded in New York in 2016, runs a 24/7 English- and Russian-speaking support line, and has crossed 100,000 active users globally. On the receiving side it integrates with every major Uzbek mobile operator (Beeline, Ucell, Mobiuz/UMS, Uzmobile, Humans) and the main Tajik carriers, plus a long tail of internet and utility billers. From a B2B angle the most interesting partner segments are remittance fintechs targeting CIS corridors, accounting tools serving small Uzbek-American businesses, and MNO revenue-assurance teams that want a normalized inbound-top-up feed. The app is delivered on Android, iOS and a public web portal at upay.net, all of which share the same backend and therefore the same integration surface.
Screenshots
Click any thumbnail to view the full-resolution screen. These shots are the basis for our protocol-analysis map: each recharge form, history page and receipt corresponds to a documented data point in the integration surface above.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification for all endpoints
- Protocol & auth-flow report (OAuth-style, token, signing)
- Runnable source for login, statement, recharge and webhook receiver (Python & Node.js)
- Postman / Insomnia collection plus automated test suite
- Compliance pack: PCI DSS scope note, GDPR DSR template, Uzbekistan data-residency checklist
- Operator-mapping table (UZ & TJ MSISDN prefixes → operator IDs)
Recent ecosystem update (2024–2025)
In 2024 the Central Asian recharge corridor saw two notable shifts that we factor into delivery: Ucell completed its post-privatization rebranding under state control, and Humans launched as a digital-first MVNO targeting the same diaspora audience uPay.net serves. Both required updates to our MSISDN-prefix → operator mapping and added new SKUs to the catalogue feed; the integration ships with a versioned operator table so partners do not need to redeploy when the next operator joins.
Similar apps & integration landscape
Customers integrating uPay.net often run several adjacent apps in the same wallet, remittance, or recharge category. The list below captures the broader ecosystem so partners can plan unified data flows. We treat each of these neutrally — the goal is to describe what data each app holds and how a unified integration could span them, not to compare them.
Ding (DingConnect)
Global mobile top-up network covering 150+ countries and 700+ operators, with a public REST & OAuth API. Customers who use both Ding and uPay.net often need a unified recharge ledger across operators and corridors.
doctorSIM
Spain-based international top-up service that also serves the Uzbekistan corridor. Complements uPay.net for partners who need fallback routing or multi-vendor pricing comparisons.
Rebtel
Stockholm-based calling and top-up app aimed at the diaspora segment. Holds outbound-call CDR-style data alongside recharge history — a useful join key for "who calls and tops up the same number" analyses.
BOSS Revolution
IDT Corporation's calling and money-transfer brand, popular with US-based diaspora users. Combining its remittance ledger with uPay.net's recharge ledger gives a fuller view of household support flows.
Monito Top-up
Comparison and recharge marketplace; relevant when partners want both a price-comparison feed and a transactional recharge surface.
CLICK (Uzbekistan)
One of the two largest domestic payment apps in Uzbekistan, with millions of installs. Holds local card and wallet data that complements uPay.net's cross-border perspective.
Payme.uz
Uzbekistan-domestic payment super-app. Useful for unified domestic-plus-cross-border views of the same household.
Paynet (Uzbekistan)
One of the oldest fintech operators in Uzbekistan, originally agent-network-based. Carries utility and ISP biller data that overlaps with uPay.net's biller catalogue.
OSON
Uzbek payment app with a focus on integrating international payment organizations — an interesting bridge between domestic wallets and inbound diaspora flows.
Beepul / Apelsin
Operator- and bank-affiliated payment apps (Beeline UZ and Kapital Bank respectively). Their recharge and bill-payment histories naturally pair with uPay.net's cross-border recharge ledger when building a 360-degree household-spend picture.
About OpenFinance Lab
We are an independent technical studio focused on App interface integration, authorized API integration and OpenData / OpenFinance / OpenBanking work. Our engineers come from banks, payment gateways, MNO billing platforms and protocol-analysis teams, and have shipped integrations across remittance, e-commerce, OTT and financial-data corridors.
- Cross-border remittance and recharge protocol work, with a strong CIS-corridor track record
- Authorized API design, OAuth bridging and webhook fan-out
- Custom Python / Node.js / Go SDKs and a documented test harness for each delivery
- Full pipeline: protocol analysis → spec → build → validation → compliance review
- Source-code delivery from $300 — runnable code plus full documentation; pay only after you accept the delivery
- Pay-per-call API billing — call our hosted endpoints with no upfront fee, ideal for usage-based teams
Contact
For a quote or to submit your target app and requirements, open our contact page:
Two engagement models: source-code delivery (from $300, pay on satisfaction) or pay-per-call hosted API.
Engagement workflow
- Scope confirmation — pick the integration surface (login, statements, recharge initiation, webhooks, biller catalogue).
- Protocol analysis & API design (2–5 business days, complexity-dependent).
- Build, internal validation and operator-mapping QA (3–8 business days).
- Documentation, sample apps and automated test cases (1–2 business days).
- Typical first delivery: 5–15 business days; carrier or PSP approvals may extend timelines.
FAQ
What do you need from me to start the uPay.net integration?
How long does delivery take for a uPay.net Mobile Recharge integration?
How do you handle compliance for remittance and recharge data?
Which payment methods can the integration cover?
📱 Original app overview (appendix)
UPAYNET is a modern and secure mobile recharge service that lets users send credit to mobile phones, internet service providers, utilities and many other services in Uzbekistan and Tajikistan. Anyone living, studying or working abroad can top up their family's and friends' accounts quickly, safely and conveniently. The company was founded in 2016 in New York and already has more than 100,000 users around the world; the team works daily to improve service quality and to add new destination countries and operators.
- Top up accounts of all cellular operators in Uzbekistan, Tajikistan and the USA;
- Payment of internet service providers in Uzbekistan and Tajikistan;
- Payment of utility services in Uzbekistan and Tajikistan;
- Payment for various other services and providers in Uzbekistan and Tajikistan;
- Multiple payment methods: Visa, MasterCard, Discover, American Express, PayPal and others;
- Personal information and payment details kept secure;
- Transaction history available directly on the phone;
- Convenient and simple interface;
- Ability to save favorite numbers;
- Automatic payments and instant delivery after billing-information verification;
- Reliable platform for sending minutes to Uzbekistan;
- Leader in mobile recharges sent from abroad to Uzbekistan and Tajikistan.
Official website: upay.net · Telegram: t.me/ezpayme · Facebook: facebook.com/upaynet · Instagram: instagram.com/upaynet · 24/7 customer support: +1 877 7738355, +1 718 5032282 · Email: support@upay.net, info@upay.net