How to Choose a Crypto Payment Provider: 10 Questions

Comparison pages rank providers on fee percentages and coin counts, which are the two least useful signals available. Here are ten questions that actually separate them, and how AIO answers each one.

1. Are my funds in wallets tied to my account, or in a shared pot?

Pooled custody puts every merchant's balance in shared wallets with an internal ledger recording who owns what. It is simpler to build, and it means one merchant's situation becomes structurally everyone's.

AIO: every merchant gets wallets tied to their own account. Your balance is identifiable on-chain and separate from everyone else's.

2. Where do the private keys live?

Keys in application code, a config file or a database mean anyone who reaches the server reaches the money. What you want is signing that happens inside a boundary the key never crosses.

AIO: private keys are held in HSM and KMS. Signing happens inside that boundary and the key itself never leaves it, so it cannot be extracted from the application layer. Hot balances are kept deliberately small and separated from the rest.

3. Are callbacks signed, and is the scheme documented?

If your server cannot prove a webhook came from your provider, anyone who finds the endpoint can tell your system an order was paid.

AIO: every callback is HMAC signed, and the scheme is documented at docs.aio.cash so your server can verify before it acts. Requests going the other way are signed too, with a timestamp inside the signed string so a captured request cannot be replayed later.

4. Is every deposit screened, and what happens to a flag?

Receiving funds with a bad history becomes the recipient's problem, not the sender's, and every banking and ramp relationship you will ever want depends on being able to show how inbound flow is checked.

AIO: deposits are screened with Crystal Intelligence and AMLBot before they reach your balance, and anything flagged is held for review rather than swept in quietly. AIO sets the thresholds and owns the decision.

5. What happens when a customer underpays, overpays, or sends an unconfigured token?

The most revealing question on the list, because it is about the unhappy path and most platforms have not thought about it.

AIO: underpayment and overpayment follow rules you configure in advance, with a tolerance so a payment a few cents short does not fail. A token you have not configured is recorded as an UnknownSubTransaction and bound to your account after review, so the funds are recoverable rather than lost.

6. Can I control who on my team can move money?

Most real losses happen through a login rather than a cipher.

AIO: sub-users with role-based permissions, two-factor enforced on every operator account, IP allow-listing for the organisation, and API keys that are scoped and rotatable. Every action lands in an audit trail that answers who did this and when.

7. What does a month of my actual volume cost, all in?

Not the headline percentage. Platform fee plus network cost, and whether transfers are batched, because unbatched payouts can quietly cost more than the entire platform fee.

AIO: a 0.3% base fee on pay-ins with loyalty discounts below it, and 0% on payouts, and the network side is engineered down rather than passed straight on. Payouts go out in batches so one fee covers a run instead of one fee per recipient, Tron transfers use rented energy, and on Bitcoin and Litecoin many transfers are packed into a single P2TR SegWit transaction.

8. Which chains, and can the customer pay on the one they already use?

The count is not the point. Not making your customer bridge is the point, because every added step is a step somebody abandons.

AIO: all chains, with the same integration shape on each. Your customer pays where they already hold funds and you are settled in USDT or USDC either way. Every chain and token, with the contract address for each, is published at aio.cash/currencies.

9. What do I get on every transaction?

An internal reference only your provider can resolve puts you back to taking their word for it.

AIO: the transaction hash, on every transaction, alongside the fiat value at settlement. Both sides can verify it on any block explorer without asking anyone.

10. Who answers at 2am?

Ask concretely. A shared channel with engineers, or a form with a target response time?

AIO: a shared group on Slack, Telegram or whichever channel you already use, opened when you onboard. You talk to the team directly, typically inside five minutes, and the shifts cover every hour.

How to read the answers

Length is the signal. A team that built the thing answers these in a sentence each, because they made the decision and remember making it.

Ask all ten before you integrate. Every one of them is cheap to ask now and expensive to discover later, and any provider worth using will answer them without a sales call. If you want to put these to AIO directly, the team is here.

Frequently Asked Questions

What should I look for in a crypto payment provider?

Segregated per-merchant wallets, private keys held in HSM and KMS, HMAC signed callbacks, deposit screening before funds are credited, role-based access with enforced two-factor, transparent total cost including network fees, and support you can actually reach. AIO answers all ten in a sentence each.

How does AIO manage private keys?

Private keys are held in HSM and KMS. Signing happens inside that boundary and the key never leaves it, so it cannot be extracted from the application layer. Hot balances are kept deliberately small and separated from the rest of the funds.

How do I compare crypto payment gateway fees?

Compare the total rather than the headline percentage, because unbatched transfers can cost more than the platform fee itself. AIO charges a 0.3% base fee on pay-ins with loyalty discounts below it, and 0% on payouts, and batches payouts, rents energy on Tron and packs Bitcoin and Litecoin transfers into single P2TR SegWit transactions so the network side stays small.

What happens if a customer sends a token that is not configured?

On AIO it is recorded as an UnknownSubTransaction and bound to your account after review, so the funds are recoverable. Under and overpayments follow rules you set in advance, with a tolerance so a payment a few cents short does not fail.