> **Qand** Partners should be aware that **new fields and/or values** may appear > in requests and responses over time. > Any unrecognised fields and/or values **must be ignored** if they are not relevant to the Partner. --- ## Overview **Qand** is a platform for processing cross-border money transfers. Partners integrate with Qand via API and initiate transfers. Qand handles all operational complexity: routing, validation, status tracking, and interaction with payment infrastructure. Partners do not need to deal with the specifics of national payment systems or differences in protocols. **For the Partner, Qand is the single integration point.** All interaction takes place through the API described in this document. --- ## Transfers Qand supports CREDIT transfers: The Partner debits funds from the sender on their side; Qand credits funds to the recipient. ``` Partner (debit) → Qand → Recipient (credit via Qand) ``` For this transfer type, the key parameters are: the settlement currency with the Partner (debit currency - `senderCurrencyCode`) and the recipient's credit currency (`receiverCurrencyCode`). --- ## Payment Instruments A payment instrument is the details by which Qand identifies the recipient for crediting. Available instruments: - Card number - Phone number + short bank code --- ## Authentication and Headers ### Required Header (all methods) | Header | Description | |---|---| | `X-Api-Key` | Partner key in UUID format. Issued upon onboarding to the platform. | --- ## Onboarding and Testing ### Network Connection (production environment) The **IPSec** protocol is used for connections in the production environment. Before integration: 1. Request the IPSec configuration form and connection settings from your account manager. 2. Provide your account manager with the IP addresses from which requests will be sent to Qand. The test environment is accessible directly from the Internet. ### Test Environment - **Base URL:** provided by your account manager during onboarding. - **Postman Collection for CREDIT transfers:** request from your account manager. - **Credentials** (`X-Api-Key` for the test environment): request from your account manager. --- ## Interaction Flow ### Optional Step: Currency Conversion - `POST /convert` Preliminary amount calculation and current exchange rate retrieval. - This method **does not create a transfer** - it is an informational request only. - Can be used by the Partner to display preliminary transfer terms to the end client. - **Not a required step** before `POST /register`.

--- ### Optional Step: Get Available Recipient Banks - `POST /info/v1/get_banks` Returns a list of banks (short bank codes) where an active card was found for the specified recipient phone number. This method is needed **only when crediting by phone number** (payment instrument `PHONE`): in this case, a short bank code (`bankLabel`) must be provided alongside the phone number. The method allows the Partner to determine in advance which banks have an active card for the recipient, and to offer the client a choice. The list of bank names corresponding to short bank codes: download. - This method **does not create a transfer** - it is an auxiliary informational request. - **Not a required step**: if the Partner obtains the bank code by other means (e.g. the client selects the bank themselves), this method may be skipped. - Currently, only **Uzbekistan** (`UZB`) is supported as the recipient's country. **Typical use-case:** 1. The client enters the recipient's phone number 2. The Partner calls `POST /info/v1/get_banks` → receives the list of banks with active cards 3. The client selects the necessary bank from the list 4. The Partner sends `phoneNumber` + `bankLabel` in the `target` field when calling `POST /register` --- ### Main CREDIT Transfer Flow ``` POST /register → POST /process ``` A CREDIT transfer requires just two steps. Once `POST /process` completes successfully, Qand automatically credits the funds to the recipient. | Step | Method | Required | Description | |---|---|---|---| | 1 | `POST /register` | Required | Transfer registration: data validation and transfer entity creation | | 2 | `POST /process` | Required | Initiates transfer processing | --- The current transfer status can be requested at any time via `POST /get_status`. Qand also sends a **callback** with the final transfer result to the URL agreed upon during onboarding. #### Asynchronous Result (code 2000) In some cases, Qand cannot return the final result synchronously. In such cases, the method will return code **2000** ("Request accepted. Wait for operation processing information in Callback or request status"). When this occurs, the Partner must either: - wait for the **callback** from Qand, **or** - poll the transfer status via `POST /get_status`.

--- ## CREDIT Transfer Status Model

| Status | Description | |---|---| | `INIT` | Transfer initiated - `POST /register` request received | | `REGISTERED` | Transfer successfully registered | | `PROCESSING` | Transfer is being processed - `POST /process` request received | | `SUCCESS` | Transfer successfully completed | | `FAILED` | Transfer rejected | | `CANCELLED` | Transfer cancelled (no further requests received to continue processing) | --- ## Settlement Report Qand automatically generates a **daily settlement report** and sends it to the list of email addresses provided by the Partner in advance. ### File Format - Format: **CSV** - Delimiter: **`;`** - First row: field names - File name: `Qand_transfers_YYYYMMDD.csv`, where `YYYYMMDD` is the export date ### Settlement Report Fields | Field | Description | |---|---| | `transfer_id` | Transfer identifier in Qand | | `transfer_created_at` | Transfer creation date and time | | `transfer_sender_amount` | Transfer amount in the sender's currency (minor units, excluding fee) | | `sender_currency` | Sender's currency (ISO 4217 alpha-3) | | `transfer_receiver_amount` | Transfer amount in the recipient's currency (minor units, excluding fee) | | `receiver_currency` | Recipient's currency (ISO 4217 alpha-3) | | `route_name` | Transfer direction | | `transfer_fee_amount` | Fee amount in the fee currency (minor units). May be negative (Partner reward) | | `fee_currency` | Fee currency (ISO 4217 alpha-3) | | `transaction_type` | Transfer type: CREDIT | | `transfer_exchange_rate` | Exchange rate fixed for the transfer (Sender's currency -> Recipient's currency) | | `payment_system` | Recipient's payment system for СREDIT-transfer (если применимо для платежного инструмента) | ### How the Partner is Reflected in the Settlement Report For a **CREDIT transfer**, the Partner acts as the **sender**: `Sender_Currency` = `Fee_Currency` = settlement currency with the Partner. --- ## Country-Specific Transfer Details ### Uzbekistan

Transfer Limits

Limits apply to cards issued in Uzbekistan. **By amount:** - Minimum transfer amount - 1 UZS - Single transaction limit - 18 749 999 UZS - Cumulative limit over the last 30 days - 9 999 USD **By number of transfers:** - Per day — maximum 5 transfers - Per month — maximum 150 transfers

Supported Card BINs

| Payment System | BINs | |---|---| | **UZCARD** | 5440, 5614, 6262, 6263, 6264, 8600 | | **HUMO** | 4008, 4027, 4062, 4067, 4073, 4097, 4198, 4294, 4728, 4790, 5555, 9860 | | **Visa** | 49169903 |