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 Fiscalization API

In this section, the API provides methods for working with fiscal receipts.`/v2/receipt` method allows you to register a sale operation and generate a fiscal receipt that complies with all legal requirements.`/v2/refund_receipt` method is designed for registering return transactions for goods or services. Similar to the direct receipt fiscalization method, it ensures the generation of a fiscal receipt for the return that also meets all regulatory requirements and can be provided to the customer.`/v2/receipt/{operation_id}/receipt_url` method provides the ability to obtain an electronic copy of the fiscal receipt using the unique operation identifier.

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

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

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

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

3 operations 3 paths 19 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 3

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

Fiscalization 3

In this section, the API provides methods for working with fiscal receipts.

POST
/v2/receipt
/v2/receipt
fiscal_receipt_generation_fiscal_receipt_generation_post 1 param body → 200202400403422500
POST
/v2/refund_receipt
/v2/refundreceipt
fiscal_receipt_refund_fiscal_receipt_refund_post 1 param body → 200202400403404422500
GET
/v2/receipt/{operation_id}/receipt_url
/v2/receipt/{operationid}/receipturl
get_receipt_url 2 params → 200202400403404422500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are ReceiptDataItem (10 properties), ReceiptData (10 properties), RefundData (8 properties), ValidationError (3 properties). Each schema is shown below with its type and property counts.

RequestAccepted
object
3 properties 2 required
BadRequestResponse
object
2 properties 2 required
ReceiptDataItem
object
10 properties 6 required
NotFoundByPaymentIdResponse
object
1 property 1 required
BadRefundRequestResponse
object
1 property 1 required
ValidationError
object
3 properties 3 required
InternalServerErrorResponse
object
1 property 1 required
ReceiptDataCommissionInfo
object
2 properties
RefundData
object
8 properties 6 required
GetReceiptURLResponse
object
1 property 1 required
NotFoundByPAOResponse
object
1 property 1 required
ReceiptRefundResponse
object
2 properties 2 required
HTTPValidationError
object
1 property
NoURLForPrepaidCreditReceipt
object
1 property 1 required
RefundAccepted
object
2 properties 2 required
AuthErrorResponse
object
1 property
ReceiptData
object
10 properties 5 required
ReceiptGenerationResponse
object
3 properties 2 required
WaitingForReceiptURLResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-fiscalization-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 From Uzbekistan API
Uzum Information retrieval API
Uzum Managing Credit Cards Bindings API
Uzum Methods API
Where this information came from

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