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 Transfer process API

Methods used in the transfer process

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

Requests are made against a single base URL, https://remit-core.ipt-merch.com.

6 operations 6 paths 47 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Uzum Transfer process API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (XApiKeyAuth).

  • XApiKeyAuth — Partner API key in UUID format. Issued upon onboarding. Required for all methods

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.

Transfer process 6

Methods used in the transfer process

POST
/v1/register
Transfer registration
registerTransfer body → 200401403422500
POST
/v1/process
Initiate transfer processing
processTransfer body → 200401403422500
POST
/v1/get_status
Get transfer status
getStatus body → 200401403422500
POST
/v1/confirm
Confirm transfer
confirm body → 200401403422500
POST
/v1/resend_otp
Resend OTP for transfer confirmation
resendOtp body → 200401403422500
POST
/v1/cancel
Cancel transfer
cancel body → 200401403422500

Schemas 47

The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are TransferResult (12 properties), PersonData (9 properties), TransferRequest (8 properties), TransferData (7 properties). Each schema is shown below with its type and property counts.

TransferRequest
object
8 properties 5 required
TransferResultStatusForProcess
object
1 property 1 required
ResendOtpResponse
object
3 properties 2 required
ProcessTransferResponse
object
3 properties 2 required
TransferResultStatusForNeedConfirmationProcess
object
1 property 1 required
DebitTargetInstrument
Payment instrument identifying the recipient's account for a DEBIT transfer. The Partner uses this to indicate the destination account on their side
TransferIdRequest
object
1 property 1 required
422ErrorResponse
object
3 properties 2 required
TransferResultStatusForGetStatus
object
1 property 1 required
CreditTransferRequest
Request body for CREDIT transfer registration. The Partner debits the sender independently; Remit Core credits the recipient.
ConfirmPendingTransferResponse
object
3 properties 2 required
TransferResultStatusForRegister
object
1 property 1 required
ThreeDsExtraFields
object
3 properties
StatusTransferResponse
object
4 properties 2 required
TransferResultStatusForCancel
object
1 property 1 required
StatusTransferRequest
object
At least one of transferId or externalTransferId must be provided
2 properties
DebitSourceInstrument
Payment instrument identifying the sender for a DEBIT transfer. Remit Core uses this to debit funds from the sender
ErrorDetails
object
2 properties 2 required
TransferResultStatusForResendOtp
object
1 property 1 required
PI.MaskedCard
object
Payment instrument - masked card number. Used in source for CREDIT transfers or target for DEBIT transfers
2 properties 2 required
PI.Account
object
Payment instrument - bank account number. Used in source for CREDIT transfers or target for DEBIT transfers
2 properties 2 required
ConfirmationData
object
3 properties 1 required
SenderPersonDataExtraFields
object
Additional sender identification fields required for DEBIT transfers from Uzbekistan
2 properties
TransferResultStatusForCancelPending
object
1 property 1 required
CancelTransferResponse
object
3 properties 2 required
IdentityDocument
object
Identity document details
7 properties
TransferResult
object
12 properties 4 required
DebitTransferRequest
Request body for DEBIT transfer registration. Remit Core debits the sender; the Partner credits the recipient independently.
CreditTargetInstrument
Payment instrument identifying the recipient for a CREDIT transfer. Remit Core uses this to credit funds to the recipient
RegisterTransferResponse
object
3 properties 2 required
TransferData
object
Financial parameters of the transfer. Exactly one of the following must be provided: - senderAmount - if the sender wants to send a fixed amount - receiverAmou…
7 properties 4 required
ProcessPendingTransferResponse
object
3 properties 2 required
PI.Card
object
Payment instrument - full card details for debit authorization. Used in source for DEBIT transfers
5 properties 4 required
PI.Phone
object
Payment instrument - recipient's phone number with bank label. Used in target for CREDIT transfers when crediting by phone number. To obtain the list of availa…
3 properties 3 required
ErrorResponse
object
3 properties 2 required
TransferResultStatusForProcessPending
object
1 property 1 required
TransferResultStatusForInfoCallback
object
1 property 1 required
CancelPendingTransferResponse
object
3 properties 2 required
TransferResultStatusForConfirmPending
object
1 property 1 required
PI.CardPan
object
Payment instrument - full card number (PAN). Used in target for CREDIT transfers when crediting by card number
2 properties 2 required
TransferResultStatusForConfirm
object
1 property 1 required
ConfirmTransferResponse
object
3 properties 2 required
PersonData
object
9 properties
TransferResultInfoCallback
Final transfer result delivered asynchronously
CreditSourceInstrument
Payment instrument identifying the sender's account for a CREDIT transfer. The Partner uses this to indicate the source account on their side. Optional. If pro…
ConfirmTransferRequest
object
2 properties 2 required
NeedConfirmationProcessTransferResponse
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-transfer-process-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 Cross-border payments 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
#Transfer process
← Back to U APIs
API Details
ID
uzum:uzum-transfer-process-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-transfer-process-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uzum-transfer-process-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 Transfer process 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.