For a business comparing payment providers in Tajikistan, a useful starting point is the merchant's side of the transaction: who receives the money, what the customer can use, and what finance can reconcile afterwards. A demonstration of a successful personal transfer answers only part of that brief.
Tajikistan's Unified QR scheme makes this distinction especially useful. A common customer interface still leaves the merchant with decisions about acquiring, pricing, reporting and business payouts. Those details belong in the provider comparison before integration starts.
Unified QR: compare the merchant service behind the code
The National Bank of Tajikistan describes Unified QR as a common format for merchant payments across banking apps and wallets. Interbank payments use the instant-payment module of its automated interbank transfer system, which the bank describes as operating continuously. National Bank of Tajikistan: Unified QR FAQ.
For a proposed collection service, ask the provider to demonstrate the exact merchant code with the customer apps relevant to your audience. Include a payment from the acquiring institution's own app and one from another participating institution. Record the recipient displayed to the buyer and the merchant-side evidence returned for each transaction.
This is a practical acceptance test. It should establish whether the quoted service is merchant acquiring, which apps participate in that arrangement, and how a successful payment appears in the merchant's records. A screenshot of a customer's transfer is insufficient evidence for that decision.
Buyer charges and merchant costs belong in different columns
In its Unified QR FAQ, the NBT says that neither the financial institution nor the merchant charges the buyer a commission for that payment. The statement addresses the buyer. It does not establish the complete commercial price of a merchant's acquiring agreement. NBT: customer charges, question 6.
Ask for an itemised merchant quote covering collection charges, any account or service fees, refund treatment and movement of funds to the intended settlement account. Specify whether costs are deducted per transaction, netted from settlement or billed separately. Confirm the applicable terms for the particular service and business.
Use a simple hypothetical test: an order is TJS 500 and the customer pays TJS 500. Ask the provider to show how that order would appear in its merchant report, the bank account and any separate fee invoice. If an agreed fee applies, identify its entry. If none applies, obtain confirmation of that scope. No actual tariff is assumed in this example.
The useful output is an explanation of gross receipts, deductions and usable funds that your finance team can reproduce.
Qualify Korti Milli for the channel you will launch
Korti Milli also needs a specific acceptance brief. As a public example of channel distinctions, Alif describes POS/QR merchant acquiring separately from website acceptance, while its online-acquiring page explicitly lists Korti Milli support. These are that bank's published product descriptions, not a claim about the capabilities of unnamed offers in PayStar's research. Alif: merchant acquiring, Alif: online acquiring.
For your shortlist, request the supported issuers and card products for the intended channel. Check the checkout flow, authentication, transaction limits, cancellation rules and refund process. Confirm which functions are available under your merchant agreement rather than assuming that a card accepted at a terminal will work in every online integration.
Keep personal card transfers separate in the brief. The required business outcome is an attributable merchant receipt with agreed records and remedies. The ability to send money to a card does not establish that commercial arrangement.
| Requirement | Evidence to request |
|---|---|
| Unified QR collections | Merchant recipient, participating customer apps and transaction confirmation |
| Korti Milli acceptance | Channel, supported issuers/products and agreed refund procedure |
| Merchant accounting | Gross amount, fee treatment, settlement reference and bank-account credit |
| TJS business payouts | Eligible beneficiary type, destination details, funding and completion evidence |
Test TJS payouts separately, including another bank
An incoming-payment service leaves an independent question: how will the business pay an eligible recipient? The NBT's January–June 2026 overview distinguishes intrabank payments, direct correspondent arrangements and payments through accounts held at the central bank. That is a reason to establish the proposed path rather than treating every TJS transfer as operationally identical. NBT: payment system overview.
Build the payout test around your real purpose, such as a supplier payment or an approved customer refund. Confirm eligible beneficiary categories, required account or card details, funding currency, amount limits and the evidence of receipt. Request separate examples for the same institution and another institution where the proposed service supports them.
Ask how a rejected destination, delayed confirmation or returned payment is handled. Identify who investigates it, which reference finance retains and what happens to the original order. An outgoing transfer should not automatically close an outstanding refund in your own records.
If the business or treasury account is overseas, qualify that structure separately: contracting entity, receiving account, permitted activity, conversion and any onward remittance. This guide does not establish foreign-merchant eligibility or cross-border settlement availability.
Turn the requirement into a focused shortlist
PayStar's 14 September 2026 snapshot contains 28 unique recorded payment offers linked only to Tajikistan. This is a dated research inventory; it does not count independent providers or establish active connections, approval or current availability. Country, currency and method associations alone do not prove a usable combination.
PayStar Discovery can help structure the comparison around the merchant entity, sales channel, customer methods, TJS collection and payout requirements, and expected transaction sizes. The merchant selects and contracts directly with the PSP; the PSP remains responsible for processing and settlement under that agreement.
Want information about these payment options for free? Just write to us. Email Anastasia or contact Anastasia on Telegram. Free information does not mean free integration, processing or guaranteed approval.
Offer snapshot: 14 September 2026. Public sources checked: 21 September 2026.