Back to home

Legal

Refund & Cancellation Policy

What we can and cannot reverse. This page explains when a refund is possible, in which currency it is returned, how long it takes, and how to raise a dispute. It sits alongside the Terms & Conditions, the Platform Rules, and the Risk Disclosure.

Last updated: September 7, 2026

1. Scope and definitions

This Refund & Cancellation Policy applies to payments and settlements initiated through FastXP2P — Scan & Pay, Card Pay, buy and sell orders, deposits, withdrawals, and utility payments. It must be read together with the Terms & Conditions and the Platform Rules.

  • Transaction — a payment you initiate in the app, where USDT is debited from your wallet and an INR settlement is made to the merchant, beneficiary, or QR you scanned.
  • Settlement — the INR payout to the destination UPI ID, QR, bank account, or biller.
  • Trade lock — the USDT held aside from your available balance while a request is live. It is released back to you automatically if the request is cancelled or expires unpaid.
  • Cancellation window — the period after you submit a request but before the INR settlement has been dispatched.
  • Refund — the return of value to you in USDT or INR after a transaction has failed, been rejected, or been reversed.

2. When a refund is allowed

A refund is considered in the following situations:

  • Failed transaction — your USDT was debited but the INR settlement could not be completed at all.
  • Rejected transaction — the beneficiary bank, UPI handle, or biller rejected or returned the settlement.
  • Delayed transaction — the settlement remains incomplete beyond the stated window and cannot be completed on retry.
  • Duplicate transaction — the same payment was settled more than once because of a system or user duplication, and the extra amount is recoverable.
  • Debited but not settled — value left your wallet and no corresponding settlement exists.

Refunds are reviewed on evidence: the on-chain transaction hash, the app reference ID, the UTR of the INR leg, and the settlement status recorded by FastXP2P.

3. When a refund is not allowed

You are responsible for the details you enter and the QR you scan. FastXP2P cannot reverse a correctly executed transaction.

  • You scanned the wrong QR, or paid the wrong merchant or person.
  • You entered the wrong amount and the settlement completed successfully.
  • You sent USDT to a wrong address, on an unsupported network, or on a network other than the one displayed on the deposit screen.
  • You sent a token other than the one requested, or sent to a deposit address after it expired.
  • You paid a dynamic or time-limited QR whose validity had run out — see section 4 below.
  • The merchant delivered nothing, delivered late, or you are unhappy with the goods or services purchased. That is a dispute with the merchant, not with FastXP2P.
  • Any transaction that has been settled as instructed and confirmed by the beneficiary bank or on-chain.

Warning:Wrong QR, wrong address, or wrong network is the user's responsibility. Blockchain transfers are irreversible, and funds sent that way usually cannot be recovered by anyone, including FastXP2P.

4. Expired and dynamic QR codes — no refund guarantee

Always use a static QR in Scan & Pay — a shop counter QR or a personal UPI QR that carries no countdown, no session, and no pre-filled one-time amount. Static QRs stay valid, so a settlement made against them always reaches the intended beneficiary.

Dynamic QRs — generated by a billing machine, POS terminal, payment gateway checkout, or any screen showing a timer — are valid only for a short window at the beneficiary's end. A Scan & Pay request is fulfilled by a merchant, which takes time, and that countdown is outside our control.

  • If you pay a QR that has already expired, the transaction is not eligible for a refund.
  • If the QR carried a time limit that ran out while the payment was being made, but the merchant has already paid the INR out, the money has left our side. In that situation we do not guarantee a refund, because recovery depends entirely on the beneficiary bank or gateway returning the funds.
  • If such a settlement is in fact returned by the beneficiary bank, we will pass the recovered amount back to you, less network and banking charges. If it is not returned, nothing can be recovered.
  • The same applies to one-time payment links, session-bound checkout QRs, and QRs that accept only a single payment.

By confirming a Scan & Pay payment you accept this policy and confirm that the QR you scanned is a static shop or personal QR.

5. Refund currency

  • Where your USDT was debited but no INR settlement was made, the refund is normally returned in USDT to your FastXP2P wallet.
  • Where an INR settlement was dispatched and later returned by the beneficiary bank, the refund may be issued in INR to the source account, or converted back to USDT, at FastXP2P's discretion.
  • INR refunds are only sent to the account the funds originated from. We do not refund to third-party accounts.
  • We do not refund in cash, gift cards, or any asset other than USDT or INR.

6. Exchange rate used for refunds

Where a refund requires converting between INR and USDT, the rate applied is the FastXP2P rate at the moment the refund is processed — not the rate of the original transaction.

  • Crypto prices move. A refund may therefore be worth more or less in INR than the original transaction.
  • USDT refunded to your wallet is returned as the same token quantity where the settlement never occurred, less applicable network fees.
  • FastXP2P does not compensate for market movement, rate difference, or depeg between the transaction and the refund.

7. Network and third-party charges

  • Blockchain network and gas fees are paid to the network, not to FastXP2P, and cannot be refunded.
  • Where a refund is sent on-chain, the network fee required to broadcast it is deducted from the refund amount.
  • Bank, biller, or third-party processor charges incurred on a returned settlement are deducted where applicable.
  • Platform fees confirmed on a completed transaction are non-refundable. Where a transaction fully failed, any platform fee charged on it is returned with the principal.

8. Refund processing timeline

  • Requests are acknowledged and reviewed within 24 hours of being raised on our official Telegram support.
  • Approved USDT refunds are credited to your wallet, or broadcast on-chain, within 24 hours of approval. On-chain confirmation then depends on the network.
  • Approved INR refunds are typically credited within 3–5 business days of approval, subject to banking timelines.
  • Cases requiring bank tracing, beneficiary confirmation, or merchant reconciliation may take longer. We will keep you updated on the same thread.

9. Partial and pending transactions

  • A pending transaction is not eligible for a refund until it is finally resolved as settled or failed.
  • If only part of a payment settled, only the unsettled portion is eligible.
  • If you underpay a deposit request, the shortfall is either topped up by you or the received amount is returned, less network fees.
  • If you overpay, the excess is returned in USDT to your wallet, less network fees.
  • Do not raise a chargeback, a bank dispute, or a parallel complaint while a case is open with us — it delays resolution.

10. Automatic refunds

An automatic refund is a system-initiated return of value that happens without you having to raise a request. It is triggered only when all of the following are true:

  • Your USDT was locked or debited for a request created inside the app.
  • The INR settlement was never dispatched, or was dispatched and returned in full by the beneficiary bank.
  • The originating wallet or account is known and valid.
  • No compliance hold, dispute, investigation, or risk review is open on the transaction.

A Scan & Pay request that no merchant completes before its timer runs out is released automatically: the locked USDT returns to your available balance and no settlement is made. An automatic refund returns the received amount less unavoidable network charges. Anything that does not meet these conditions is handled as a manual refund request under this policy.

11. Cancellation

  • You may cancel a request in the app while it is still unclaimed and no merchant has paid — nothing has moved, nothing is owed, and the trade lock is released in full.
  • A short lock applies immediately after a request is created, so that merchants who were notified are not left chasing a request that vanishes. The cancel button becomes available as soon as that period ends.
  • Once USDT has been broadcast on-chain, the transfer cannot be cancelled by FastXP2P.
  • Once the INR settlement has been dispatched, the transaction cannot be cancelled. It becomes a refund case only if the settlement is returned.
  • FastXP2P may cancel or decline a request before settlement for compliance, risk, rate, or liquidity reasons. Funds held for it are returned under the automatic refund process.

12. Disputes and complaints

Raise every refund or settlement issue in the order chat on the transaction itself, or on our official Telegram support at t.me/fastxp2p. Do not deal with anyone claiming to be FastXP2P on another handle.

What to include:

  • The app transaction / reference ID.
  • The on-chain transaction hash and network used, or the UTR of the INR leg.
  • The amount, date, and time (with time zone).
  • A screenshot of the QR or payment screen, and any error message.

Our response:

  • Acknowledgement within 24 hours.
  • Investigation outcome communicated as soon as verification with the network, bank, or merchant is complete.
  • If you are not satisfied with the outcome, reply on the same thread asking for escalation and a senior reviewer will look at the case again.

Warning: FastXP2P will never ask for your recovery phrase, private keys, or wallet login to process a refund. Anyone asking for those is attempting fraud.

13. Related documents

Before you transact, please also read the Terms & Conditions, the Platform Rules, and the Risk Disclosure.

Have a question about this document? Reach us on Telegram.