Uzum CrossBorder Transfer

openapi: 3.0.0
info:
  title: Uzum CrossBorder Transfer
  version: 0.1.0
  description: >
    **Uzum CrossBorder Transfer** is an international money transfer service
    between Uzbekistan and other countries. It allows users to send and receive
    transfers by phone number or card number through a single, secure API.


    #### ⚙️ Key features

    - Transfers **to** Uzbekistan by phone number and card number

    - Transfers **from** Uzbekistan by card number

    - Cross-border payments for services in Uzbekistan

    - Retrieval of current exchange rates

    - Transfer status checks

    - Access to the registry of completed transfers


    #### ⚠️ Important

    - Availability of individual API features depends on the cooperation terms
    and is enabled by agreement with Uzum Bank. To enable the required operation
    types or clarify the methods available to you, contact your Uzum Bank
    manager.

    - The specification may change. Check the [Updates](#section/Updates)
    section for changes.

    - To check the status:
      - for a transfer, use [/transfer/status](#tag/Common-methods/operation/transferStatus);
      - for a payment, use [/payment/status](#tag/Cross-border-payments/operation/getPaymentStatus).
      - the response returns either the current operation status or an error if the operation was not received by the service:
        - `10212` for transfers;
        - `2xxxx` for payments.
    - Successfully credited funds cannot be refunded.

    - Funds debited from a UZ card as part of a transfer from Uzbekistan may be
    canceled if the crediting on the recipient side was not completed (see the
    [/cancel_debit](#tag/From-Uzbekistan/operation/cancelDebit) method).


    #### 🚀 **Quick start**

    - [Network connection setup](#section/Network-Setup)

    - [Authorization](#section/Authorization)

    - [Get exchange rates](#tag/Common-methods/operation/convert)

    - [Transfer to Uzbekistan](#tag/To-Uzbekistan)

    - [Transfer from Uzbekistan](#tag/From-Uzbekistan)

    - [Cross-border payment for services in
    Uzbekistan](#tag/Cross-border-payments)

    - [Check transfer status](#tag/Common-methods/operation/transferStatus)


    ---

    ## Getting started

    To integrate with the **CrossBorder Transfer API** quickly and smoothly,
    follow these steps:


    1. **Set up network access and authorization**  
        - Configure the [network connection](#section/Network-Setup) to Uzum Bank.
        - Obtain and securely store the [authorization token](#section/Authorization) from your Uzum Bank account manager.

    2. **Review limits and supported banks**  
        - Check the applicable [transfer limits](#section/Transfer-Limits).
        - Review the list of [supported banks in Uzbekistan](#section/List-of-Supported-Banks-in-Uzbekistan).

    3. **Review key processes**:
        - [Exchange rate handling](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Calculation-of-the-Preliminary-Transfer-Amount)
        - [Transfer to Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-to-Uzbekistan)
        - [Transfer from Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-from-Uzbekistan)
        - [Cross-border payment for services in Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Cross-border-Payment-for-Services-in-Uzbekistan)

    4. **Run a test integration**  
      Use the provided [test environment](#tag/Testing) to verify that all scenarios work as expected.

    5. **Go live**  
      After successful testing, you will receive access to the production environment and can move the integration to live operation.

    ## Network Setup


    The <a href="https://aws.amazon.com/what-is/ipsec/"
    target="_blank">IPSec</a> protocol is used to establish a network connection
    with Uzum Bank.


    IPSec is used in the production environment; the test environment is
    accessible over the internet.


    Before integration, please fill out <a
    href='/crossborder/IPSec_form_UzumBank_over_BCC.xlsx'>this form</a> and
    provide your manager with the IP addresses that will be used to send
    requests to Uzum Bank.


    ## Transfer Limits

    Limits are determined based on Uzbekistan-issued debit cards.


    ### Amount Limits

    - Minimum transfer — 1 tiyin (0.01 UZS).

    - Maximum single transfer amount — 19,999,999 UZS.

    - Cumulative 30-day — 9,999 USD.


    ### Limits on the Number of Transfers

    - Day — 5 transfers.

    - Month — 150 transfers.


    ### Increasing the Single Transfer Limit

    If you can provide additional recipient information, the single transfer
    limit can be increased. To request a limit increase, please contact your
    Uzum Bank manager.


    Additional information includes:

    - Series and number of the identity document (e.g., passport, ID card, or
    other equivalent document)

    - Sender’s address (as stated in the identity document)

    - Date of birth

    - Place of birth

    - Citizenship


    Providing additional information significantly reduces the likelihood of
    transfer rejections during compliance checks.


    ## Authorization


    Authorization is done via the HTTP <a
    href="https://developer.mozilla.org/en/docs/Web/HTTP/Headers/Authorization"
    target="_blank">Authorization</a> header, which must be in every request.
    The header is generated using the "Basic" scheme and user credentials
    encoded in <a href="https://developer.mozilla.org/en/docs/Glossary/Base64"
    target="_blank">base64</a> format: `Authorization: Basic <user
    credentials>`. The user credentials, including the username and password,
    are provided by our team.


    To form the header:


    1. Create a string from the username and password, separated by a colon, for
    example: `"myLogin:myPassword"`;

    2. Encode the string in base64, the result might be
    `YWxhZGRpbjpvcGVuc2VzYW1l`;

    3. Insert the result into the header; make sure there is a space between the
    word `"Basic"` and the encoded credentials.


    The header will look like:


    | Header      | Value                        |

    |--------------------|------------------------------|

    | Authorization | Basic YWxhZGRpbjpvcGVuc2VzYW1l    |


    ## Forming JSON Body


    ⚠️ If a field is not required and you do not plan to populate it, **do not
    include this field** in the request. An empty value is interpreted as a
    **submitted field with an error**.


    ## Working with Currency Rates


    Using the method
    [/cbt/v1/transfer/convert](#tag/Common-methods/operation/convert), you can
    request the currency exchange rate and display approximate debit and credit
    amounts to the sender. The rate depends on the recipient's payment system,
    and the exact calculation will be performed during the transfer feasibility
    check using methods
    [/cbt/v1/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit) or
    [/cbt/v1/transfer/check_dedit](#tag/From-Uzbekistan/operation/checkDebit).


    If you plan to display approximate debit and credit amounts, please inform
    the user that these are approximate amounts, and the exact amounts will be
    provided in the next step.


    ## List of Supported Banks in Uzbekistan


    To perform transfers using a phone number, you must provide the sender with
    a list of supported banks in the recipient's country. The current list of
    banks in Uzbekistan is <a
    href='/crossborder/en_bank_label_list_crossborder_transfers.xlsx'>available
    in the table</a>. The `BANK_LABEL` field is required in the request
    [/cbt/v1/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit)
    for phone number transfers.


    ### Supported BINs


    **BIN (Bank Identification Number)** refers to the first 4–8 digits of the
    **PAN (Primary Account Number)** that identify the payment system and the
    card-issuing bank.


    Only cards with the BINs listed below are accepted for crediting funds to
    Uzbekistan.


    #### UzCard

    <a href="/crossborder/uzcard_bins_clean.txt" download> Download list BIN
    UzCard </a>


    #### HUMO

    <a href="/crossborder/humo_bins_clean.txt" download> Download list BIN HUMO
    </a>


    #### Visa Uzum Bank


    PAN starts with: `49169903`



    # Interaction Processes Between Your Service and Uzum Bank


    The interaction processes include:


    - [Calculation of the preliminary transfer
    amount](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Calculation-of-the-Preliminary-Transfer-Amount)

    - [Transfer to
    Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-to-Uzbekistan)
      - [Transfer using the recipient's phone number](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-to-Uzbekistan/Transfer-Using-the-Recipient's-Phone-Number)
      - [Transfer using the card number](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-to-Uzbekistan/Transfer-Using-the-Card-Number)
    - [Transfer from
    Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Transfers-from-Uzbekistan)

    - [Cross-border payment for services in
    Uzbekistan](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Cross-border-Payment-for-Services-in-Uzbekistan)
      - [Working with the service list and payment fields](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Cross-border-Payment-for-Services-in-Uzbekistan/Working-with-the-Service-List-and-Payment-Fields)

    ## Calculation of the Preliminary Transfer Amount


    <a href='/img/crossborder/crossborder-convert-eng.png' target='_blank'><img

    src='/img/crossborder/crossborder-convert-eng.png'/></a>.


    1. The user enters the transfer amount in the debit currency.


    2. The service sends a request to Uzum Bank for currency conversion
    [/cbt/v1/transfer/convert](#tag/Common-methods/operation/convert). The
    available currency pairs are:

      - RU - UZS
      - USD - UZS
      - EUR - UZS

      <br>
      
      **OR**

    1. The user enters the transfer amount in the credit currency, UZS.


    2. The service sends a request to Uzum Bank for currency conversion
    [/cbt/v1/transfer/convert](#tag/Common-methods/operation/convert):

      - UZS - RU 
      - UZS - USD 
      - UZS - EUR

      <br>

    3. Uzum Bank returns a response with the converted amount.


    4. The service provides the user with a screen displaying the converted
    amounts.


    ## Transfers to Uzbekistan

    ### Transfer Using the Recipient's Phone Number


    <a href='/img/crossborder/crossborder-by-phone-eng.png' target='_blank'><img

    src='/img/crossborder/crossborder-by-phone-eng.png'/></a>.


    1. The user enters the recipient's phone number.


    2. The service requests banks with the recipient's active cards linked to
    the phone number using the
    [/cbt/v1/transfer/receiver_banks](#tag/To-Uzbekistan/operation/getReceiverBanksList)
    method.


    3. Uzum Bank searches for banks with the recipient's active cards and
    returns them as a list.


    4. The service displays the recipient's banks.


    5. The user selects a bank.


    6. The user enters the transfer amount in the debit currency.


    7. The service sends a request to Uzum for a transfer feasibility check
    [/cbt/v1/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit),
    specifying the debit amount, recipient's phone number, and recipient's bank.


    8. Uzum Bank verifies the cards and limits, conducts compliance and
    anti-fraud procedures to ensure maximum transfer security.


    9. Uzum Bank returns information about the feasibility of the transfer, the
    credit amount in UZS, and the debit amount in the debit currency.


    10. The service provides the user with transfer information for review.


    11. The user confirms the transfer.


    12. The service sends a confirmation request to Uzum Bank
    [/cbt/v1/transfer/confirm_credit](#tag/To-Uzbekistan/operation/confirmCredit).
    To confirm the transfer, the operation must have the status `APPROVED`. ⚠️
    We do not send callbacks for transfers with the `PENDING` status. If you
    receive this status, request the transfer state using the
    [/transfer/status](#tag/Common-methods/operation/transferStatus) method
    every hour until a final status (`SUCCESS` or `FAILED`) is returned.


    13. Uzum Bank credits the funds to the card.


    14. Uzum Bank returns information about the successful transfer.


    ```
      If Uzum Bank returns an error, the process cannot continue. You need to handle the error and re-initiate the debit process. You should also initiate the cancellation of the failed payment in your system.
    ```


    15. The service provides the user with the transfer result.


    ### Transfer Using the Card Number


    <a href='/img/crossborder/crossborder-by-card-eng.png' target='_blank'><img

    src='/img/crossborder/crossborder-by-card-eng.png'/></a>.


    1. The user enters the card number, first name, and last name of the
    recipient in Latin script.


    2. The user enters the transfer amount in the debit currency.


    3. The service sends a request to Uzum for a transfer feasibility check
    [/cbt/v1/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit),
    specifying the credit amount and the card number.


    4. Uzum Bank verifies the cards and limits, conducts compliance and
    anti-fraud procedures to ensure maximum transfer security.


    5. Uzum Bank returns information about the feasibility of the transfer, the
    credit amount in UZS, and the debit amount in the debit currency.


    6. The service provides the user with transfer information for review.


    7. The user confirms the transfer.


    8. The service sends a confirmation request to Uzum Bank
    [/cbt/v1/transfer/confirm_credit](#tag/To-Uzbekistan/operation/confirmCredit).
    To confirm the transfer, the operation must have the status `APPROVED`. ⚠️
    We do not send callbacks for transfers with the `PENDING` status. If you
    receive this status, request the transfer state using the
    [/transfer/status](#tag/Common-methods/operation/transferStatus) method
    every hour until a final status (`SUCCESS` or `FAILED`) is returned.


    9. Uzum Bank credits the funds to the card.


    10. Uzum Bank returns information about the successful transfer.

        ```
        If Uzum Bank returns an error, the process cannot continue. You need to handle the error and re-initiate the debit process. You should also initiate the cancellation of the failed payment in your system.
        ```

    11. The service provides the user with the transfer result.


    ## Transfers from Uzbekistan


    <a href='/img/crossborder/crossborder-from-uz-eng.png' target='_blank'><img

    src='/img/crossborder/crossborder-from-uz-eng.png'

    style="display: block; margin: 0 auto; max-width:100%; height: auto;"/></a>


    1. The user enters the card number, first name, and last name of the
    recipient in Latin.

    2. The user specifies the transfer amount in UZS.

    3. The service sends a request to Uzum Bank to register the transfer using
    the method
    [/cbt/v1/transfer/check_debit](#tag/From-Uzbekistan/operation/checkDebit).

    4. Uzum Bank performs anti-fraud checks to ensure the security of the
    transfer.

    5. Uzum Bank updates the transaction status to "APPROVED."

    6. Uzum Bank returns information about the transfer's feasibility, including
    the debit amount in UZS and the credit amount in the destination currency.

    7. Uzum Bank sends an OTP to the user's number.

    8. The service displays transfer information and a field for entering the
    OTP.

      If a resend of the OTP is required:
      - The service sends a request to resend the OTP using the method [/cbt/v1/transfer/resend_otp](#tag/From-Uzbekistan/operation/resendOTP).
      - Uzum Bank resends the OTP to the user.

    9. The user enters the received OTP.

    10. The service sends a request to Uzum Bank to confirm the transfer with
    the OTP using the method
    [/cbt/v1/transfer/confirm_debit](#tag/From-Uzbekistan/operation/confirmDebit).
    To confirm the transfer, the operation must have the status `APPROVED`. ⚠️
    We do not send callbacks for transfers with the `PENDING` status. If you
    receive this status, request the transfer state using the
    [/transfer/status](#tag/Common-methods/operation/transferStatus) method
    every hour until a final status (`SUCCESS` or `FAILED`) is returned.

        In case of an incorrect OTP:
      - Uzum Bank returns an error indicating the number of attempts left.
      - The service notifies the user of the error and the remaining attempts.
      - The user enters a new OTP, and the process repeats.

    11. Uzum Bank updates the transaction status to "PENDING."

    12. Uzum Bank debits the funds.

    13. Uzum Bank updates the transaction status to "SUCCESS."

    14. Uzum Bank sends information about the successful transfer.

        If Uzum Bank does not respond:
      - The service sends a request for the transaction status using the method [/cbt/v1/transfer/status](#tag/Common-methods/operation/transferStatus).
      - Uzum Bank returns the current transaction status.

    15. The service displays the transfer result to the user.


    ## Transfers from Uzbekistan via Tokenized Linked Cards


    We return the card token in the response to the debit confirmation request
    [/cbt/v1/transfer/confirm_debit](#tag/From-Uzbekistan/operation/confirmDebit).
    You can use this token to link the card to the user in your application and,
    for subsequent debits, send only the `senderCardToken` parameter instead of
    `senderCardPan` and `senderCardExpireDate`.


    ## Cross-border Payment for Services in Uzbekistan


    To enable **cross-border payments for services in Uzbekistan**, contact your
    Uzum Bank manager. Access to this operation type is enabled separately and
    depends on the cooperation terms.

    > Please also clarify the current and complete list of payable services with
    your manager. Through the API, the partner receives only the services
    available within the enabled functionality.


    <a href='/img/crossborder/crossborder_payment.png' target='_blank'><img

    src='/img/crossborder/crossborder_payment.png'/></a>.


    1. The partner requests the list of available services from Uzum Bank using
    [/cbt/v1/payment/service_list](#tag/Cross-border-payments/operation/getServiceList).
    The response can be stored on the partner side so that service fields do not
    need to be requested for every payment attempt.

    2. Uzum Bank returns the list of services available for payment.

    3. The user selects a service on the partner side and fills in the required
    details.

    4. If the payment amount is set in the partner's currency, the partner can
    calculate the UZS amount in advance using
    [/cbt/v1/transfer/convert](#tag/Common-methods/operation/convert). The
    cross-border payment flow also supports exchange rate calculation on the
    partner side: in this case, the partner sends the amount in its own currency
    and the exchange rate in payment requests.

    5. If the selected service requires checking the details and receiving a
    specific payment amount, the partner sends the details to Uzum Bank using
    [/cbt/v1/payment/check_service](#tag/Cross-border-payments/operation/checkService).

    6. Uzum Bank checks the details and returns the calculated payment amount in
    UZS and in the partner's currency.

    7. If the service allows an arbitrary amount, the partner can skip
    `/check_service` and create the payment immediately.

    8. The partner creates the payment using
    [/cbt/v1/payment/check_payment](#tag/Cross-border-payments/operation/checkPayment).
    The payment amount in the request is always sent in UZS.

    9. Uzum Bank returns the created payment data and the current operation
    status.

    10. The partner debits the user on its side.

    11. After a successful debit, the partner confirms the payment in Uzum Bank
    using
    [/cbt/v1/payment/confirm_payment](#tag/Cross-border-payments/operation/confirmPayment).

    12. Uzum Bank executes the payment and returns the result: payment status
    and the fiscal receipt link `ofdUrl`.

    13. If the payment status is not final, the partner additionally requests
    the current status using
    [/cbt/v1/payment/status](#tag/Cross-border-payments/operation/getPaymentStatus).

    14. For reconciliation, the partner requests the payment registry using
    [/cbt/v1/payment/payment_list](#tag/Cross-border-payments/operation/getPaymentList).


    ### Working with the Service List and Payment Fields


    Get the service list using
    [/cbt/v1/payment/service_list](#tag/Cross-border-payments/operation/getServiceList).
    The method accepts the page number and limit:


    ```json

    {
      "page": 1,
      "limit": 20
    }

    ```


    The response returns the `serviceList` array and the `paginationResponse`
    object. The service list changes rarely, so it can be cached on the partner
    side.


    A `service` object describes the service and the fields that must be shown
    to the user:


    ```json

    {
      "serviceId": 224,
      "name": "Tashkent city",
      "minAmount": 500,
      "maxAmount": 5000000,
      "isFixedAmount": false,
      "fields": []
    }

    ```


    | Field | Description |

    |-------|-------------|

    | `serviceId` | Service identifier. Send it in all subsequent payment
    requests. |

    | `name` | Service name to display to the user. |

    | `minAmount` / `maxAmount` | Allowed payment amount range in tiyin. |

    | `isFixedAmount` | If `true`, do not show the amount input to the user:
    receive the amount from
    [/cbt/v1/payment/check_service](#tag/Cross-border-payments/operation/checkService)
    and send it to
    [/cbt/v1/payment/check_payment](#tag/Cross-border-payments/operation/checkPayment).
    If `false`, the user enters the amount in the `minAmount`-`maxAmount` range.
    |

    | `fields` | Payment form fields that must be filled before calling
    `/check_service` or `/check_payment`. |


    Each object in `fields` describes one form field:


    ```json

    {
      "key": "customer_code",
      "title": "Customer account",
      "type": "S",
      "regex": "^\\d{6,10}$",
      "values": []
    }

    ```


    | Field | Description |

    |-------|-------------|

    | `key` | Field key. Send it in `serviceParameters.key`. |

    | `title` | Field name to display to the user. |

    | `type` | Field type. Allowed values: `S` for string, `N` for number, `E`
    for a value selected from the `values` dictionary. |

    | `regex` | Regular expression for validating the value. If `regex` is not
    set, no additional pattern validation is required. |

    | `values` | Value dictionary for fields with type `E`. Send the selected
    item's `code` in the request, not `name`. |


    #### Displaying Fields to the User


    - For `S`, show a text input.

    - For `N`, show a numeric input and apply `regex` if it is set.

    - For `E`, show a dropdown built from `values`; display `name` to the user
    and send `code` in the request.


    Example of passing filled fields:


    ```json

    {
      "serviceId": 224,
      "serviceParameters": [
        {
          "key": "soato",
          "value": "26262"
        },
        {
          "key": "customer_code",
          "value": "1234567890"
        }
      ]
    }

    ```


    Before calling
    [/cbt/v1/payment/check_service](#tag/Cross-border-payments/operation/checkService),
    we recommend checking that all fields are filled, values match `regex` if it
    is set, and the amount is within `minAmount`-`maxAmount` if `isFixedAmount:
    false`.


    # State Model


    The state model below applies to:

    - transfers to Uzbekistan;

    - transfers from Uzbekistan;

    - cross-border payments for services in Uzbekistan.


    ⚠️ **Note**: the `REVERSED` status is used only for transfers from
    Uzbekistan and means that the debit was canceled using
    [/cbt/v1/transfer/cancel_debit](#tag/From-Uzbekistan/operation/cancelDebit).
    Currently, cancellation is not supported for transfers to Uzbekistan or
    cross-border payments.


    <a href='/img/crossborder/crossborder_to_uz_state_model.png'
    target='_blank'><img

    src='/img/crossborder/crossborder_to_uz_state_model.png'

    style="display: block; margin: 0 auto; max-width:70%; height: auto;"/></a>


    | Status     | Description |

    |------------|-------------|

    | REGISTERED | Initial status after calling
    [/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit),
    [/transfer/check_debit](#tag/From-Uzbekistan/operation/checkDebit), or
    [/payment/check_payment](#tag/Cross-border-payments/operation/checkPayment).
    |

    | APPROVED   | The
    [/transfer/check_credit](#tag/To-Uzbekistan/operation/checkCredit),
    [/transfer/check_debit](#tag/From-Uzbekistan/operation/checkDebit), or
    [/payment/check_payment](#tag/Cross-border-payments/operation/checkPayment)
    method was successfully executed. |

    | PENDING    | The
    [/transfer/confirm_credit](#tag/To-Uzbekistan/operation/confirmCredit),
    [/transfer/confirm_debit](#tag/From-Uzbekistan/operation/confirmDebit), or
    [/payment/confirm_payment](#tag/Cross-border-payments/operation/confirmPayment)
    method was called. We do not send callbacks for operations with the
    `PENDING` status. If you receive this status, request the transfer state
    using [/transfer/status](#tag/Common-methods/operation/transferStatus) or
    the payment state using
    [/payment/status](#tag/Cross-border-payments/operation/getPaymentStatus)
    every hour until a final status (`SUCCESS` or `FAILED`) is returned. |

    | SUCCESS    | The transfer or payment was completed successfully. |

    | FAILED     | The transfer or payment failed. |

    | REVERSED   | The debit for a transfer from Uzbekistan was canceled using
    [/transfer/cancel_debit](#tag/From-Uzbekistan/operation/cancelDebit). |


    # Updates


    ## 30.07.2026


    - Added PDF test scenarios for cross-border payments for services in
    Uzbekistan to [Testing](#tag/Testing): mock testing and real integration
    with suppliers.

    - Added a note to [Testing](#tag/Testing) that partners must contact
    technical support before running mock test cases.

    - Updated the
    [/payment/service_list](#tag/Cross-border-payments/operation/getServiceList)
    and
    [/payment/payment_list](#tag/Cross-border-payments/operation/getPaymentList)
    response schemas: `services` and `payments` were renamed to `serviceList`
    and `paymentList`, and `pagination` was renamed to `paginationResponse`.

    - Updated the `ServiceField.type` enum in [Working with the Service List and
    Payment
    Fields](#section/Interaction-Processes-Between-Your-Service-and-Uzum-Bank/Cross-border-Payment-for-Services-in-Uzbekistan/Working-with-the-Service-List-and-Payment-Fields)
    and in the
    [/payment/service_list](#tag/Cross-border-payments/operation/getServiceList)
    response schema: allowed values are `S`, `N`, `E`; `ServiceField.regex` and
    `Service.isFixedAmount` can now be `null`.


    ## 16.07.2026


    - Clarified the [/check_credit](#tag/To-Uzbekistan/operation/checkCredit)
    method description: for transfers by recipient phone number
    (`identificationType = PHONE`), the `bankLabel` parameter is required. A
    phone-number transfer cannot be performed without `bankLabel`; no default
    card is selected for crediting.

    - Added error codes `20101`-`20211` for cross-border payments.


    ## 15.07.2026


    - Added cross-border payments for services in Uzbekistan to the English
    specification.

    - Updated the
    [/payment/service_list](#tag/Cross-border-payments/operation/getServiceList)
    specification: the service description now includes `minAmount`,
    `maxAmount`, `isFixedAmount`, and payment fields now include the `values`
    dictionary with `code` and `name`.

    - Added instructions for working with the `service` object, field types
    `STRING`, `NUMBER`, `SELECT`, `isFixedAmount` logic, and client-side
    validation before calling
    [/payment/check_service](#tag/Cross-border-payments/operation/checkService).


    ## 13.07.2026


    - Updated the maximum single transfer amount — **19,999,999 UZS**.


    ## 30.04.2026


    - The `code` field in the
    [/confirm_debit](#tag/From-Uzbekistan/operation/confirmDebit) method now
    accepts **digits and latin characters** in both lowercase and uppercase
    (pattern: `[0-9a-zA-Z]{4,6}`). The length constraint (4–6 characters)
    remains unchanged.   


    ## 02.07.2025


    - A new identification type was added to the
    [/check_credit](#tag/To-Uzbekistan/operation/checkCredit) method:
    **`identificationType = TOKEN`** — a string containing the tokenized card
    number.  
      The `identificationValue` parameter description was updated to clarify formats for `PHONE`, `CARD`, and `TOKEN`.  
    - Added support for new currencies in the `senderCurrencyCode` and
    `receiverCurrencyCode` parameters of the
    [/check_credit](#tag/To-Uzbekistan/operation/checkCredit) and
    [/check_debit](#tag/From-Uzbekistan/operation/checkDebit) methods.  
      This works for partners who provide their own exchange rates.  
      **Supported currencies:** `UZS`, `RUB`, `USD`, `EUR`, `TJS`.


    ## 30.05.2025


    - Added information about [supported card
    BINs](#section/List-of-Supported-Banks-in-Uzbekistan) for transfers to the
    Republic of Uzbekistan.  

    - Added information about the minimum transfer amount — **1 tiyin (0.01
    UZS)**.

    - Added description for error [10317](#tag/Error-Codes).

    - Updated the request parameters object for method
    [/check_debit](#tag/From-Uzbekistan/operation/checkDebit): updated the
    **sender** and **receiver** objects.

    - Updated the textual description for method
    [/transfer_list](#tag/Common-methods/operation/transferList): The method
    returns a registry of operations for the last **2 months (60 calendar
    days)**.

    - Added methods for working with recipient cards:
      - Retrieval of [card list](#tag/To-Uzbekistan/operation/getReceiverCardsByPhone) by phone number.
      - Retrieval of [card information](#tag/To-Uzbekistan/operation/getReceiverCardsByPAN) by PAN.

    ## 15.04.2025

    - Updated the [Postman collection](#tag/Testing) with test cases.  

    - Modified the request parameter for the
    [/cancel_debit](#tag/From-Uzbekistan/operation/cancelDebit) method: the
    `cancellationReason` field has been renamed to `reason`.  

    - Updated the response structure for the `/confirm_credit`,
    `/confirm_debit`, `/cancel_debit`, `/status`, and `/check_credit` methods:
    the `paymentSystem` field is now called `receiverPaymentSystem`.  

    - Revised and clarified the [error descriptions](#tag/Error-Codes).  

    - Added information about the [transfer volume
    limits](#section/Transfer-Limits). Day — 5 transfers. Month — 150
    transfers. 

    - Updated the [transfer status model](#section/State-Model): a new
    `REVERSED` status has been added — it is assigned when a credit is cancelled
    using the [/cancel_debit](#tag/From-Uzbekistan/operation/cancelDebit)
    method.



    | Status     |
    Description                                                        |

    |------------|--------------------------------------------------------------------|

    | REGISTERED | Initial status after calling the `/check_credit` or
    `/check_debit` method.          |

    | APPROVED   | The `/check_credit` or `/check_debit` method was successfully
    executed.             |

    | PENDING    | The `/confirm_credit` or `/confirm_debit` method was called.
    ⚠️ We do not send callbacks for transfers with the PENDING status. If you
    receive this status, request the transfer state using the
    [/transfer/status](#tag/Common-methods/operation/transferStatus) method
    every hour until a final status (`SUCCESS` or `FAILED`) is returned. |

    | SUCCESS    | The credit was successfully
    completed.                            

# --- truncated at 32 KB (130 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/uzum/refs/heads/main/openapi/uzum-crossborder-openapi.yaml