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

Uzum Methods API

QR CRM methods that are used to create an order, check the status of the order and transfer links to the fiscal receipt and cancel payment transactions.

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

The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 9 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against the base URL https://crossborder.transfer.uz.

9 operations 9 paths 18 schemas 8 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://crossborder.transfer.uz
Resource Areas
1

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 8 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Methods 9

QR CRM methods that are used to create an order, check the status of the order and transfer links to the fiscal receipt and cancel payment transactions.

POST
/api/dynamic-qr/merchant/payment/create
Create Order
create_order body → 200401
POST
/api/dynamic-qr/merchant/payment/status-by-order
Check Order
check_order body → 200401
POST
/api/dynamic-qr/merchant/payment/fiscal
Fiscal
fiscal body → 200401
POST
/api/dynamic-qr/merchant/payment/reversal
Reverse
reversal body → 200401
POST
/api/dynamic-qr/merchant/payment/cancel-order
Cancel order
cancel_order body → 200401
POST
/api/apelsin-pay/merchant/v2/payment
Payment
payment body → 200401
POST
/api/apelsin-pay/merchant/payment/fiscal
Fiscalization
postApiApelsinPayMerchantPaymentFiscal body → 200401
PUT
/api/apelsin-pay/merchant/v2/payment/reversal/{orderId}
Payment Cancellation
putApiApelsinPayMerchantV2PaymentReversalByOrderId 1 param body → 200401
POST
/api/apelsin-pay/merchant/payment/status
Payment status
status body → 200401

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are PaymentResponse (7 properties), CheckOrderResponse (6 properties), PaymentRequest (6 properties), CreateOrderRequest (4 properties). Each schema is shown below with its type and property counts.

CancelResponse
object
4 properties 3 required
CreateOrderRequest
object
4 properties 3 required
FiscalRequest
object
3 properties 3 required
ReversalRequest
object
2 properties 2 required
ReversalResponse
object
3 properties 3 required
CancelRequest
object
2 properties 2 required
FiscalResponse
object
3 properties 3 required
CheckOrderRequest
object
2 properties 2 required
CheckOrderResponse
object
6 properties 3 required
CreateOrderResponse
object
2 properties 2 required
FiscalRequest_2
object
3 properties 3 required
ReversalRequest_2
object
2 properties 2 required
ReversalResponse_2
object
3 properties 3 required
StatusResponse
object
3 properties 3 required
PaymentRequest
object
6 properties 6 required
PaymentResponse
object
7 properties 6 required
StatusRequest
object
2 properties 2 required
FiscalResponse_2
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-methods-api-openapi.yml Raw ↑

Other APIs Uzum publishes across the network.

Uzum BaaS Payment Hub
Uzum Market Seller API
Uzum API MFO API
Uzum Auxiliary Methods API
Uzum Back-to-back Payment API
Uzum Check Service Status API
Uzum Common methods API
Uzum Cross-border payments API
Uzum Fiscalization API
Uzum From Uzbekistan API
Uzum Information retrieval API
Uzum Managing Credit Cards Bindings API
Where this information came from

This is an independent, third-party profile of Uzum Methods 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.