How to Receive Crypto Payments
Rift Research
Last updated
TLDR: The cheapest receive is the asset and chain the payer already holds. That inbound transfer is a send. Convert after it lands. Rift is an aggregator with best price execution. After settlement, Rift converts on its supported chains at 0 added fee.
Most “0% fee” checkout products hide the conversion inside a spread.
Short version
| Goal | Do this |
|---|---|
| Least friction | Publish one address per chain you actually use |
| Single treasury unit (USDC) | Accept what they send, then convert |
| Many source chains | Aggregator on conversion, not a custom invoice token |
Three rules
- Native beats wrapped. If they can send USDC on Base, take USDC on Base.
- One receiving asset per chain.
- Convert after settlement, unless you have measured the checkout spread.
Robinhood Wallet’s own support copy is the same idea on the consumer side: send on the network the destination supports. See Send, receive, and swap crypto.
Other options, then Rift
Processors and invoice widgets are fine when you have priced the spread. CCTP is the default convert when both ends are native USDC (Circle CCTP). Across or Relay when speed pays for itself.
Then Rift. Payer sends USDT on Ethereum. You want USDC on Arbitrum. That is one quote. Rift includes CCTP and the other rails on Bitcoin, Ethereum, Arbitrum, Base, Hyperliquid, RobinhoodChain, Tempo, XLayer, Ink and Pharos. If they win, you get that rate with no Rift markup.
Do not publish a Bitcoin address for an ERC-20 send. Do not accept a random memecoin “because it is crypto.”