How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Uzum

Uzum CrossBorder Transfer

International money transfer between Uzbekistan and other countries. Transfers to Uzbekistan by phone number or card number, transfers from Uzbekistan by card number, cross-border payments for services inside Uzbekistan, live FX conversion rates, transfer status checks, partner account balance and operation registry. HTTP Basic authentication issued per partner.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 20 operations across 20 paths, organized into 4 resource areas, and defines 51 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

Requests are made against a single base URL, https://crossborder.transfer.uz.

20 operations 20 paths 51 schemas 2 GET18 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://crossborder.transfer.uz
Authentication
HTTP Basic
Resource Areas
4

Authentication & Security 1

Uzum CrossBorder Transfer declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 20

Across 20 paths, the API surfaces 20 operations — 2 GET, 18 POST. They span 4 resource areas: Cross-border payments, To Uzbekistan, From Uzbekistan, Common methods. Each is listed below with its method, path, parameters, and response codes.

Cross-border payments 6

Methods for cross-border payments for services in Uzbekistan

POST
/cbt/v1/payment/check_service
Get Information About the Future Payment Amount
checkService body → 200400500
POST
/cbt/v1/payment/check_payment
Run Pre-payment Checks and Create a Cross-border Payment
checkPayment body → 200400500
POST
/cbt/v1/payment/confirm_payment
Confirm a Cross-border Payment
confirmPayment body → 200400500
POST
/cbt/v1/payment/status
Get Payment Status
getPaymentStatus body → 200400500
POST
/cbt/v1/payment/service_list
Get the List of Services Available for Payment
getServiceList body → 200400500
POST
/cbt/v1/payment/payment_list
Get Payment Registry
getPaymentList body → 200400500
To Uzbekistan 5

Methods for transfers to Uzbekistan

POST
/cbt/v1/transfer/card_list
Retrieve the list of cards by phone number
getReceiverCardsByPhone body → 200400401403
POST
/cbt/v1/transfer/card
Retrieve card information by PAN
getReceiverCardsByPAN body → 200400401403
POST
/cbt/v1/transfer/receiver_banks
Get the recipient's list of banks
getReceiverBanksList body → 200401403404500
POST
/cbt/v1/transfer/check_credit
Check Possibility of Transfer to Uzbekistan
checkCredit body → 200400401403
POST
/cbt/v1/transfer/confirm_credit
Confirm Transfer to Uzbekistan
confirmCredit body → 200400401403
From Uzbekistan 4

Methods for transfers from Uzbekistan

POST
/cbt/v1/transfer/check_debit
Register Transfer from Uzbekistan and Send OTP
checkDebit body → 200400401403
POST
/cbt/v1/transfer/resend_otp
Resend OTP
resendOTP body → 200400401403408
POST
/cbt/v1/transfer/confirm_debit
Confirm Transfer from Uzbekistan
confirmDebit body → 200400401403
POST
/cbt/v1/transfer/cancel_debit
Cancel Transfer
cancelDebit body → 200400401403
Common methods 5
POST
/cbt/v1/transfer/convert
Get Currency Conversion Rates
convert body → 200400401403
POST
/cbt/v1/transfer/status
Get Payment Status
transferStatus body → 200400401403
POST
/cbt/v1/transfer/transfer_list
Get Transfer List
transferList body → 200400401403
GET
/cbt/v1/partner/account/closing_balance
Get Current Closing Balance
getClosingBalance 1 param → 200400401500504
GET
/cbt/v1/partner/account/operations
Get Account Operations
getAccountOperations 3 params → 200400401500504

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are CheckDebitRequest (16 properties), CheckCreditRequest (14 properties), TransferStatusResponse (14 properties), PaymentResponse (14 properties). Each schema is shown below with its type and property counts.

Error
object
3 properties
CheckServiceRequest
object
3 properties 3 required
CheckServiceResponse
object
7 properties 5 required
CheckPaymentRequest
object
The amount is always expected in UZS. If conversion is performed on the partner side, also send the amount in the partner currency and the exchange rate.
11 properties 7 required
ServiceParameters
object
3 properties 2 required
PaymentRequest
object
1 property 1 required
AdminPaymentResponse
object
11 properties 8 required
CheckPaymentResponse
object
Returns all payment fields available when the response is generated.
10 properties 8 required
PaymentResponse
object
Returns all payment fields available when the response is generated.
14 properties 9 required
ServiceListRequest
object
2 properties 2 required
ServiceListResponse
object
2 properties 2 required
Service
object
6 properties 3 required
ServiceField
object
5 properties 3 required
ServiceFieldValue
object
Field value dictionary item
2 properties 1 required
PaymentListResponse
object
2 properties 2 required
PaymentListRequest
object
4 properties 3 required
TransferResponse
object
12 properties 11 required
TransferCancelResponse
object
12 properties 11 required
SenderInfo
object
An object containing information about the identity of the transfer initiator.
7 properties 6 required
ReceiverInfo
object
An object containing information about the identity of the transfer recipient.
3 properties 1 required
IdentityDocument
object
An object containing information about the identity document.
6 properties 6 required
ReceiverCardsByPANRequest
object
1 property
ReceiverCardsByPhoneRequest
object
1 property
ReceiverCardsByPhoneResponse
array
CardResponse
object
6 properties 6 required
ReceiverBanksRequest
object
1 property 1 required
ReceiverBanksResponse
object
1 property
OperationInfo
object
9 properties
AccountOperationsResponse
object
6 properties
ClosingBalanceResponse
object
4 properties
PaginationResponse
object
5 properties
ErrorResponse
object
3 properties 2 required
ErrorDetails
object
2 properties 2 required
ConvertRequest
object
4 properties 4 required
ConvertResponse
object
5 properties 5 required
CheckCreditRequest
object
14 properties 8 required
PersonalData
object
6 properties 1 required
CheckCreditResponse
object
11 properties 3 required
ConfirmCreditRequest
object
2 properties 1 required
TransferStatusRequest
object
1 property 1 required
TransferStatusResponse
object
14 properties 11 required
TransferListRequest
object
5 properties 3 required
FilterTime
object
2 properties 2 required
TransferListResponse
array
CheckDebitRequest
object
16 properties 9 required
CardToken
object
1 property 1 required
CheckDebitResponse
object
8 properties 3 required
ConfirmDebitRequest
object
2 properties 2 required
CancelDebitRequest
object
2 properties 1 required
ResendOTPRequest
object
2 properties 1 required
inline_response_200
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-crossborder-openapi.yaml Raw ↑
#Money Transfer#Remittances#Cross Border#Foreign Exchange
← Back to U APIs
API Details
ID
uzum:uzum-crossborder-transfer
Base URL
https://crossborder.transfer.uz
Docs
https://developer.uzumbank.uz/en/crossborder
Provider
Uzum
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=uzum-uzum-crossborder-transfer&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uzum-uzum-crossborder-transfer"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Uzum CrossBorder Transfer, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.