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

Remit Core

Single integration point for cross-border remittances. Partners register, process, confirm, cancel and status-check CREDIT and DEBIT transfers; Remit Core handles routing, validation and interaction with national payment infrastructure. Also exposes FX conversion, recipient bank lookup by phone number, and partner balance. X-Api-Key header authentication; production connectivity is over IPSec.

Remit Core is one of 11 APIs that Uzum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Money Transfer, Remittances, and Cross Border. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 9 paths, organized into 2 resource areas, and defines 55 schemas. It is described by OpenAPI 3.0.0, at version 1.0.4.

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

9 operations 9 paths 55 schemas 9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.4
Base URL
https://remit-core.ipt-merch.com
Authentication
API Key
Resource Areas
2

Authentication & Security 1

Remit Core 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 9

Across 9 paths, the API surfaces 9 operations — 9 POST. They span 2 resource areas: Transfer process, Information retrieval. 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
Information retrieval 3

Auxiliary Information Methods

POST
/v1/convert
Convert amount and get exchange rate
convert body → 200401403422500
POST
/info/v1/get_banks
Get available recipient banks
getBanks body → 200401403422500
POST
/info/v1/get_balance
Get partner account balance
getBalance body → 200401403422500

Schemas 55

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

ConvertRequest
object
6 properties 4 required
ConvertResponse
object
3 properties 2 required
ConvertResult
object
8 properties 7 required
StatusTransferRequest
object
At least one of transferId or externalTransferId must be provided
2 properties
TransferRequest
object
8 properties 5 required
CreditTransferRequest
Request body for CREDIT transfer registration. The Partner debits the sender independently; Remit Core credits the recipient.
DebitTransferRequest
Request body for DEBIT transfer registration. Remit Core debits the sender; the Partner credits the recipient independently.
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
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
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
PI.CardPan
object
Payment instrument - full card number (PAN). Used in target for CREDIT transfers when crediting by card number
2 properties 2 required
PI.Card
object
Payment instrument - full card details for debit authorization. Used in source for DEBIT transfers
5 properties 4 required
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…
CreditTargetInstrument
Payment instrument identifying the recipient for a CREDIT transfer. Remit Core uses this to credit funds to the recipient
DebitSourceInstrument
Payment instrument identifying the sender for a DEBIT transfer. Remit Core uses this to debit funds from the sender
DebitTargetInstrument
Payment instrument identifying the recipient's account for a DEBIT transfer. The Partner uses this to indicate the destination account on their side
PersonData
object
9 properties
SenderPersonDataExtraFields
object
Additional sender identification fields required for DEBIT transfers from Uzbekistan
2 properties
IdentityDocument
object
Identity document details
7 properties
RegisterTransferResponse
object
3 properties 2 required
TransferResultStatusForRegister
object
1 property 1 required
ProcessTransferResponse
object
3 properties 2 required
TransferResultStatusForProcess
object
1 property 1 required
ProcessPendingTransferResponse
object
3 properties 2 required
TransferResultStatusForProcessPending
object
1 property 1 required
NeedConfirmationProcessTransferResponse
object
4 properties 3 required
TransferResultStatusForNeedConfirmationProcess
object
1 property 1 required
ConfirmationData
object
3 properties 1 required
ThreeDsExtraFields
object
3 properties
ConfirmTransferResponse
object
3 properties 2 required
TransferResultStatusForConfirm
object
1 property 1 required
ConfirmPendingTransferResponse
object
3 properties 2 required
TransferResultStatusForConfirmPending
object
1 property 1 required
ResendOtpResponse
object
3 properties 2 required
TransferResultStatusForResendOtp
object
1 property 1 required
CancelTransferResponse
object
3 properties 2 required
TransferResultStatusForCancel
object
1 property 1 required
CancelPendingTransferResponse
object
3 properties 2 required
TransferResultStatusForCancelPending
object
1 property 1 required
StatusTransferResponse
object
4 properties 2 required
TransferResultStatusForGetStatus
object
1 property 1 required
TransferResult
object
12 properties 4 required
TransferIdRequest
object
1 property 1 required
ConfirmTransferRequest
object
2 properties 2 required
GetBanksRequest
object
2 properties 2 required
GetBanksResponse
object
3 properties 2 required
GetBanksResult
object
1 property 1 required
GetBalanceResponse
object
3 properties 2 required
GetBalanceResult
object
3 properties 3 required
422ErrorResponse
object
3 properties 2 required
ErrorDetails
object
2 properties 2 required
ErrorResponse
object
3 properties 2 required
TransferResultInfoCallback
Final transfer result delivered asynchronously
TransferResultStatusForInfoCallback
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-remitcore-openapi.yaml Raw ↑

Other APIs Uzum publishes across the network.

Uzum Checkout
Uzum CrossBorder Transfer
Uzum Nasiya Partner API
Uzum Fiscalization
Uzum Fast Pay
Uzum Dynamic QR
Uzum Merchant API
Uzum RateKeeper
Uzum BaaS Payment Hub
Uzum Market Seller API
Where this information came from

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