Crypto payment · overview
primerouter treats crypto-native as a first-class citizen — not a wrapper over a payment processor, but direct on-chain listening, on-confirmation crediting, byte-aligned ledger.
Why we built this
Traditional fiat payments:
- Cross-border fees ~3.5% + fixed
- Chargeback risk you can't control
- High-risk regions blocked
- Heavy PII collection
- T+N settlement
Crypto payments are different:
- On-chain = settled: confirmation = money
- No chargeback: transfer is final
- Globally accessible: if you can reach a chain, you can pay
- Privacy-friendly: address is your identity
- Auditable: every transfer is on a public chain, independently verifiable
Supported chains and tokens
| Chain | Type | Tokens | Default confirmations |
|---|---|---|---|
| Ethereum | EVM | USDT, USDC | 12 |
| BSC | EVM | USDT, USDC | 12 |
| Polygon | EVM | USDT, USDC | 64 |
| Arbitrum | EVM | USDT, USDC | 12 |
| Aptos | Move | USDC, APT | 5 |
The list grows over time — see Console → Top up for the latest. Confirmations are admin-tunable, balancing speed vs. safety.
Core features
On-chain credit
Once confirmations are reached, the credit automatically lands in your account balance. No human review, no support ticket.
Multi-chain, multi-token
A single account can use multiple chains and tokens — no need to maintain separate accounts per chain.
Uniqueness constraint prevents double credit
primerouter uses (chain_id, tx_hash, log_index) as a strong uniqueness constraint — the same on-chain transfer never credits twice.
Auto + on-demand dual mode
- Auto scan (admin-configured): the service continuously listens to new blocks
- On-demand sync: from the console, users can trigger "sync my transfers" to scan recent blocks for a specific address
Together you get low-latency auto-credit plus a manual safety net.
Byte-aligned ledger
The credit amount is precisely converted from on-chain token quantity. The ledger can be matched line-by-line against the public block explorer (Etherscan / BSCScan / Aptoscan / etc.).
What's not supported (clear boundaries)
- ❌ Auto-rollback on chain reorg: once confirmations are reached, status doesn't roll back. Extreme reorg scenarios could result in mistaken credit (the confirmations depth is the safety mechanism; default 12 blocks on BSC).
- ❌ Auto refunds: chain finality means transfers are terminal. If you really need a refund, contact support for manual handling.
- ❌ Cross-chain bridging: you must transfer on the specified chain to the matching address. Wrong chain or wrong address may permanently lose funds.
Three perspectives
By role:
| You are | This page |
|---|---|
| User wanting to top up | User guide: how to top up |
| Troubleshooting top-up issues | FAQ + troubleshooting |