FAQ's

A blockchain is a shared public ledger that records every transaction and lets anyone verify it. No single bank or company controls it, and once a payment is written to the chain it cannot be edited or reversed. That is what makes it work as a payment rail: the record is the receipt.

Your customer sends funds from a wallet to an address created for that order, the network confirms the transfer in seconds, and the payment lands in your account. With AIO the customer can pay from a crypto wallet or in their local currency, and you are settled in USDT or USDC either way. One transaction hash covers the whole payment, and both sides can check it on any block explorer.

You get paid from anywhere without a bank in the middle, and the money is yours in under a minute instead of three days. There are no chargebacks, because a confirmed on-chain payment cannot be reversed later. Fees are a fraction of card rates, 0.3% on pay-ins and 0% on payouts, and you settle in stablecoins so you are not left holding the swings.

Yes. The chain is public and tamper-evident, so a confirmed payment cannot be altered or reversed. On the AIO side each merchant has segregated custodial wallets with keys in HSM/KMS, every callback is HMAC signed so your server can prove it came from us, two-factor is enforced on every operator account, and API keys are scoped, rotatable and IP allow-listed.

Tron carries the most stablecoin payment volume, mostly USDT, because transfers on it are cheap and fast. Ethereum and its layer-2s, BSC, Polygon, Solana and Bitcoin cover most of the rest. AIO runs on all of them and settles you in USDT or USDC whichever chain your customer pays on.

Yes. They pay with their normal bank account or the payment app they already use at home, in their own money. We turn that money into stablecoins (digital dollars) behind the scenes, and that is what lands in your AIO balance. Your customer never opens a crypto app, never buys a coin and never sees a wallet. Why we built it this way: most people in the world do not own crypto. If we only accepted crypto, you would only be able to sell to the small group who already have it.

“Fiat” just means normal government money, like dollars, euros or pesos. An on-ramp is the doorway that turns that normal money into digital money. Your customer pays in pesos, the on-ramp converts it, and you get paid in digital dollars. How AIO does it: the doorway sits inside your checkout, so from your customer’s side it is just a payment page in their own language and currency.

Vietnamese dong, Brazilian real, Indonesian rupiah, Philippine peso, Mexican peso, UAE dirham, Malaysian ringgit, Chilean peso, Peruvian sol, Ghanaian cedi and the euro. The full list of countries, with every bank and wallet we accept in each one, is on the fiat coverage page. Why these: we started with the markets where card payments fail most often, because that is where a merchant gains the most by adding us.

Bank transfer or a local payment app, depending on the country. In Vietnam that includes MoMo, ZaloPay, Viet QR and the major banks. In Brazil it is the local instant transfer system. In the Philippines it is the wallets people already have on their phone. Why not cards: in these markets a card is often the payment method that gets declined, and bank transfers and local wallets are what people genuinely use every day.

Stablecoins, in USDT or USDC. These are digital tokens that are always worth about one US dollar each, so the amount you were paid does not move up or down while you wait. You never hold anything whose price changes. Why it matters: if we settled you in an ordinary cryptocurrency, a sale you made on Monday could be worth less by Thursday. A payment should not turn into a bet.

A licensed payment partner does the fiat leg, not AIO. They are the ones regulated to hold and move local currency in each country, and they run the identity checks that come with it. Why we do it this way: moving local money is a regulated business in every country, and it should be done by a firm licensed to do it in that country. We handle the settlement to you, they handle the money coming in.

No account with AIO and no crypto wallet. They open the payment page, pick their bank or wallet, and pay. Depending on the amount and the country, the licensed partner may ask them for identity details, exactly as their own bank would. Why: every extra step at checkout loses you sales, so we keep it to the smallest number the law allows.

Today we take local money in. Paying local money back out is on the way. In the meantime you can pay anyone in stablecoins on any chain, and they can cash out through their own provider. Why we say this plainly: we would rather tell you what works now than have you find out at the wrong moment.

Per-merchant segregated custodial wallets; keys are held in HSM/KMS. AIO does not lend, stake, or proprietary trade client assets.

No. Movements occur only with your explicit authorization. You can configure payout thresholds and optional dual-approval.

2FA/TOTP for all operator accounts (cannot be disabled), IP allow-listing, role-based access, scoped/rotatable API keys, and HMAC-signed callbacks. Dashboard pages show API Key restrictions, callback secret reset, and audit logs/records for callbacks.

Your system creates a pay-in, the buyer pays the shown address, AIO validates the on-chain transaction and credits the correct wallet, then AIO sends a signed webhook so you can mark the order complete.

One-time pay-ins lock chain/token/amount and require exact payment. Long-term pay-ins return a reusable address with a 90-day lease that auto-renews on each deposit; if there’s no activity for 90 days it becomes Overdue and the address is deactivated until a new deposit or manual close.

Configurable by you; AIO completes the pay-in when your confirmation/threshold is met.

Under/over-payments follow your configured rules. A token you have not configured is recorded as an UnknownSubTransaction and bound to your account after review, so nothing is lost.

The base fee is 0.3% on pay-ins, with loyalty discounts below it when you commit to a monthly volume, and 0% on payouts. Gas is optimised, not just passed on: batch transfers across the chains, and rented energy on Tron.

Your system requests a payout (with chain, token, amount, to_addr). AIO broadcasts it on-chain, monitors confirmations, then sends a completion webhook. Approvals follow your threshold/dual-control settings.

Built for throughput, not one payout at a time. Payouts go out in batches, so on Tron, the EVM chains and Solana they land fast and the gas is shared across the whole batch instead of paid per transfer. On Bitcoin and Litecoin we use P2TR SegWit to pack many transfers into a single transaction, which cuts the fee hard and settles everyone at once. UTXO timing still follows network conditions.

Stablecoin settlement in USDT or USDC, on any chain. Deposits in other assets are converted to stablecoins per your configuration and compliance rules.

aio-docs.apifox.cn, covering auth, pay-in/pay-out APIs, pricing endpoints, and callback specs.

Include your API key in the header: Aio-Api-Key: <api-key>. Signatures and encryption are described in Security docs. Create and restrict keys in Dashboard > Integrations > API Management; you can set IP restrictions per key.

• List Transactions GET /v2/tx
• Get Transaction Info GET /v2/tx/info/{txid}
• Create Pay-in POST /v2/tx/pay-in
• Create Long-term Pay-in POST /v2/tx/pay-in-longtime
• Create Payout POST /v2/tx/pay-out
• Price GET /v2/price and Calculate Fiat to Crypto GET /v2/price/calc_vs_price

Configure your URL in Dashboard > Integrations > Callback Management. We send HTTP POST with headers including Algorithm: HMAC-SHA256, Body-MD5, Date, and Aio-Sign (HMAC using your secret). Implement idempotency (e.g., by tx_id/sub_tx_id). AIO retries on failure with exponential backoff (up to 16 attempts). You can reset the secret in the dashboard.

Daily/weekly/all Pay-in/Payout counters, Received/Sent tx counts, Wallet Assets by chain/token, quick Swap/Payin/Payout actions, and a Gas Saved chart.

View All Transactions, Sub Transactions, Pending, and Swap Transactions with filters, amounts/fees, and status (e.g., Pending, Completed, Overdue, Closed). Each entry links to Details.

Create/enable API keys, edit key-level restrictions (e.g., IP allow-listing), rotate/delete keys, and view request logs.

Configure Callback URL, enable/disable, reset callback secret, and review Callback Records with response codes and execution times. Callback response bodies are retained for 30 days in the records view.

TOTP/2FA is enforced and cannot be turned off. Configure IP allow-listing for the organization; only listed IPs are allowed when enabled.

Manage sub-users, roles, status, and 2FA state.

Update operator email and password.

Contact us and we’ll open a shared group on Slack, Telegram, or whichever channel you already use. You talk to the team directly, typically inside 5 minutes, and the shifts cover every hour.