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 Cross-border payments API

Methods for cross-border payments for services in Uzbekistan

Documentation Provider Profile APIs.io OpenAPI GitHub

Uzum Cross-border payments API is one of 19 APIs that Uzum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cross-Border Payments. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 6 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

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

6 operations 6 paths 19 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Uzum Cross-border payments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 POST. 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

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are PaymentResponse (14 properties), CheckPaymentRequest (11 properties), CheckPaymentResponse (10 properties), CheckServiceResponse (7 properties). Each schema is shown below with its type and property counts.

ServiceParameters
object
3 properties 2 required
PaymentListResponse
object
2 properties 2 required
PersonalData
object
6 properties 1 required
ServiceListResponse
object
2 properties 2 required
Service
object
6 properties 3 required
ErrorDetails
object
2 properties 2 required
FilterTime
object
2 properties 2 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
CheckPaymentResponse
object
Returns all payment fields available when the response is generated.
10 properties 8 required
ServiceField
object
5 properties 3 required
PaymentResponse
object
Returns all payment fields available when the response is generated.
14 properties 9 required
CheckServiceRequest
object
3 properties 3 required
PaginationResponse
object
5 properties
PaymentRequest
object
1 property 1 required
CheckServiceResponse
object
7 properties 5 required
ServiceFieldValue
object
Field value dictionary item
2 properties 1 required
PaymentListRequest
object
4 properties 3 required
ErrorResponse
object
3 properties 2 required
ServiceListRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-cross-border-payments-api-openapi.yml Raw ↑

Other APIs Uzum publishes across the network.

Uzum BaaS Payment Hub
AE Profile APIs.io
Uzum Market Seller API
AE Profile APIs.io
Uzum API MFO API
AE Profile APIs.io
Uzum Auxiliary Methods API
AE Profile APIs.io
Uzum Back-to-back Payment API
AE Profile APIs.io
Uzum Check Service Status API
AE Profile APIs.io
Uzum Common methods API
AE Profile APIs.io
Uzum Fiscalization API
AE Profile APIs.io
Uzum From Uzbekistan API
AE Profile APIs.io
Uzum Information retrieval API
AE Profile APIs.io
Uzum Managing Credit Cards Bindings API
AE Profile APIs.io
Uzum Methods API
AE Profile APIs.io
#Cross-Border Payments
← Back to U APIs
API Details
ID
uzum:uzum-cross-border-payments-api
Base URL
https://crossborder.transfer.uz
Docs
https://developer.uzumbank.uz/en/checkout
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-cross-border-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uzum-cross-border-payments-api"

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 Cross-border payments API, 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.