Developer guide
VEX Pay siteAPI reference
Browse documentation

Use your USDT balance without VEX Pay

Your VEX Pay USDT balance is yours alone. If VEX Pay is unavailable, move your funds with your backup wallet or your recovery contacts, from any Safe interface or straight from Polygonscan.

Your USDT balance does not depend on VEX Pay

Your USDT balance ("Saldo USDT" in the app) lives in a Safe smart account on Polygon; this guide calls it your wallet. Only its owners can move the money: your phone's passkey (Face ID or fingerprint) and, if you added one, your backup wallet. VEX Pay has no key to it. It cannot move, freeze or recover your funds, and it does not need to be online for you to reach them.

The app talks to Polygon through VEX Pay, and your passkey only works inside the VEX Pay app and wallet.vexpay.app. If VEX Pay is down or closes, you use your backup wallet instead: it is an owner too, it signs alone, and it works from any interface that supports Safe accounts.

  • Your wallet address. It is shown on Saldo USDT. Write it down somewhere safe; it is also on any Polygonscan link the app opened.
  • Your backup wallet. Any regular wallet you control, for example MetaMask or a hardware wallet, already added as a backup wallet and past its 24 hours.
  • A little POL in the backup wallet. Without VEX Pay nobody pays the network fee for you. 0.1 POL covers many transactions.
  • Polygon refuses a very low priority fee. It asks for at least 25 gwei. MetaMask and Safe set this for you; with a script (cast send), pass e.g. --priority-gas-price 30gwei --gas-price 60gwei.

The limits still apply

Your wallet has a spending-limit contract (the guard) that protects you if a key is stolen. It lives on Polygon, not at VEX Pay, so it applies to every interface and to every owner, including your backup wallet.

What you doWhen it happens
Send USDT to a saved address that is readyAt once, any amount
Send USDT to any other address, up to US$200 per day (UTC) in totalAt once
Send more than thatQueue it, then run it after 1 hour and within 7 days after that
Anything else: add or remove an owner, change the guard or a module, send POL or other tokensQueue it, then run it after 24 hours and within 7 days after that
Save an addressAt once while the wallet has never held money; otherwise it is ready after 1 hour
Remove a saved address, or cancel something queuedAt once
  • A transaction outside these rules is refused with NotAllowedInstantly. Queue it instead.
  • Network-fee refunds are not allowed: safeTxGas, baseGas and gasPrice must be 0. The backup wallet that submits pays the fee in POL.
  • Anyone can run a queued action once it is ready. Only an owner can queue or cancel.

Step 01

Option A: a Safe interface

Safe{Wallet} (app.safe.global) and other Safe-compatible interfaces can open your wallet with your backup wallet connected. VEX Pay is not involved; you can use any interface you trust that supports Safe accounts on Polygon.

  1. Connect your backup wallet

    Open the interface, connect MetaMask (or your hardware wallet) and choose the Polygon network.

  2. Add your wallet as an existing account

    Use "add existing Safe account" (or the interface's equivalent) and paste your wallet address. It shows your passkey and your backup wallet as owners, with 1 required confirmation.

  3. Send within the limits

    Create a USDT send to a saved address, or within today's US$200. Leave the advanced gas fields at 0 and execute it yourself with the backup wallet.

  4. Larger sends: queue first

    In the interface's transaction builder, call queue(to, value, data, operation) on your guard with to = the USDT contract, value = 0, data = the USDT transfer (see the next section), operation = 0. After 1 hour, run it with executeQueued (step 05 below).

Step 02

Option B: straight from Polygonscan

This works with nothing but polygonscan.com and your backup wallet. Because the backup wallet submits the transaction itself, it does not need to sign a separate message: the wallet accepts the sender's own approval.

  1. Open your wallet on Polygonscan

    Search for your wallet address, open Contract → Write as Proxy and click Connect to Web3 with your backup wallet.

  2. Fill in execTransaction

    Use the values in the table below. Everything except to and data is a fixed value.

  3. Write and confirm

    Click Write and confirm in your backup wallet. It pays the POL fee.

FieldValue
toThe USDT contract (0xc2132D05D31c914a87C6611C10748AEb04B58e8F), or your guard for a queue
value0
dataThe call, see the next section
operation0
safeTxGas, baseGas, gasPrice0
gasToken, refundReceiver0x0000000000000000000000000000000000000000
signatures0x + 24 zeros + your backup wallet address without 0x + 64 zeros + 01

The signature says "approved by the sender": the first 32 bytes are your backup wallet address, the next 32 are zero and the last byte is 01. It only works when that same backup wallet sends the transaction.

Step 03

Build the call

A USDT send is transfer(destination, amount). USDT has 6 decimals, so 50 USDT is 50000000. The data is 0xa9059cbb, then the destination without 0x padded with zeros to 64 characters, then the amount in hexadecimal padded to 64 characters.

Example: 50 USDTbash
# destination 0x1111111111111111111111111111111111111111, amount 50000000 = 0x2faf080
0xa9059cbb
0000000000000000000000001111111111111111111111111111111111111111
0000000000000000000000000000000000000000000000000000000002faf080
# joined into one line, with no spaces
Foundry (cast)bash
# any public Polygon RPC works, for example https://polygon-bor-rpc.publicnode.com
cast calldata "transfer(address,uint256)" 0xDESTINATION 50000000

# a larger send goes through the guard: queue(USDT, 0, <transfer data>, 0)
cast calldata "queue(address,uint256,bytes,uint8)" 0xUSDT 0 0xTRANSFER_DATA 0

To queue, send execTransaction with to = your guard and data = the queue(...) call. The guard records when it becomes ready (the Queued event shows executableAt).

Step 04

Find your guard

Your wallet stores its guard address in a fixed storage slot, so you can read it from any Polygon node without VEX Pay. The last 40 characters of the result are the guard address.

Foundry (cast)bash
cast storage 0xYOUR_WALLET 0x4a204f620c8c5ccdca3fd54d003badd85ba500436a431f0cbda4f558c93c34c8 \
  --rpc-url https://polygon-bor-rpc.publicnode.com

Step 05

Run or cancel a queued action

  1. Wait until it is ready

    1 hour for a USDT send, 24 hours for anything else. It stays runnable for 7 days after that; after that, queue it again.

  2. Run it

    Open your guard on Polygonscan, Contract → Write Contract, and call executeQueued(safe, to, value, data, operation) with your wallet address and exactly the values you queued. Any wallet can send this; it pays the POL fee.

  3. Or cancel it

    Before it runs, an owner can cancel it: execTransaction with to = your guard and data = cancel(actionHash). The actionHash is in the Queued event, or from the guard's actionHash(safe, to, value, data, operation).

Step 06

If you lost every owner: recovery contacts

Every wallet has an open-source, audited social recovery module enabled (Candide Social Recovery, 0x00480F5ecC008995469fA7e12c70Ef3DC9FEe7fD, the same address on Polygon and Amoy). If you have set up recovery contacts, they can replace the wallet's owners without you and without VEX Pay. The VEX Pay app does not add recovery contacts yet; until it does, a backup wallet is the way out.

  1. Contacts confirm the new owner

    The required number of contacts each call confirmRecovery(wallet, newOwners, newThreshold, nonce, execute) on the module, with the same new owner (for example a new wallet of yours) and threshold 1. nonce comes from nonce(wallet) on the module. The last one sets execute to true.

  2. Wait 3 days

    The recovery delay lets a current owner stop a recovery they did not ask for.

  3. Finish

    Anyone calls finalizeRecovery(wallet) on the module. The new owner then moves the funds as in options A and B, under the same limits.

Recovery does not go through the guard, so the guard can never block it. To cancel a recovery you did not ask for, an owner queues cancelRecovery() on the module (a security change, ready after 24 hours) and runs it before the 3 days end.

Addresses

ContractPolygonAmoy test network
USDT (shown as USDT0 on Polygonscan)0xc2132D05D31c914a87C6611C10748AEb04B58e8F0xE1BBFB59127d003Ca8E5Fbbac142323239aB0026 (test USDT)
GuardRead it from your wallet (step 04)0x160EdB17C5aa5055B2948D95552BF6ebaa0dc130
Recovery module (3-day delay)0x00480F5ecC008995469fA7e12c70Ef3DC9FEe7fD0x00480F5ecC008995469fA7e12c70Ef3DC9FEe7fD