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 Two-Step Payment API

The Two-Step Payment API from Uzum — 2 operation(s) for two-step payment.

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

Tagged areas include Two Step Payment. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.10.3.

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

2 operations 2 paths 14 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 2

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

Two Step Payment 2
POST
/api/v1/acquiring/complete
Confirmation of two-step payment
complete_api_v1_acquiring_complete_post 3 params body → 200
POST
/api/v1/acquiring/reverse
Reverse
reverse_api_v1_acquiring_reverse_post 3 params body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are AcquiringCallbackData (7 properties), BusinessEvent (5 properties), ApiResponse_Complete2SPResponse_ (3 properties), ReceiptGeneratedCallbackData (3 properties). Each schema is shown below with its type and property counts.

BusinessEventType
string
An enumeration.
ReverseCommand
object
2 properties 2 required
ErrorCode
integer
Complete2SPResponse
object
1 property 1 required
PaymentOperationType
string
An enumeration.
ReceiptType
string
An enumeration.
BusinessEvent
object
5 properties 5 required
Complete2SPCommand
object
2 properties 2 required
ApiResponse_ReverseResponse_
object
3 properties 1 required
ReverseResponse
object
1 property 1 required
ReceiptGeneratedCallbackData
object
3 properties 3 required
ApiResponse_Complete2SPResponse_
object
3 properties 1 required
CallbackOperationState
string
An enumeration.
AcquiringCallbackData
object
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-two-step-payment-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 Two-Step Payment 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.