Ownership makes a difference.
Merchants who want to accept stablecoins usually choose between a hosted gateway and self-hosted software that keeps keys on the server. This table sets out where recv.fund differs. The other two columns describe each category in general, not any one product.
| recv.fund | Hosted gateway | Self-hosted, keys on server | |
|---|---|---|---|
| Who holds keys | You. The only keys on the server are your hot wallets, which pay network fees, start sweeps and send payouts. Deposit addresses have no private key. | The gateway holds keys or custodies balances on your behalf. | You, but deposit keys or an extended public key sit on your server and sweep contracts hold funds. |
| Can the account be closed | No account exists with us. Nothing we run is in the path of a payment. | Yes. Onboarding, verification and the right to terminate. | No account with the vendor. |
| Deposit addresses | One permanent address per customer per chain, derived from your merchant contract (Robinhood Chain) or the recv.fund program (Solana). Customers pay it with a plain transfer. | Usually wallet-connect checkout only. | Yes, generated from keys on the server. |
| Fee model | One percentage, taken only when you sweep a deposit address to your settlement wallet. Capped at 2% and fixed in your own on-chain record at registration. No fee on customer payments, no subscription, no setup fee. | Percentage per transaction, sometimes with a monthly plan. | Varies. Often a percentage on sweeps or services. |
| Chains | Robinhood Chain and Solana. Test networks only until the mainnet contracts are deployed. | Varies by gateway. | Varies by product. |
| Source | Server, dashboard and contract repositories not public. Robinhood Chain testnet factory source verified on Blockscout. | Closed. | Open or closed, by product. |
recv.fund is non-custodial software; merchants remain responsible for their own legal obligations. Product details for other categories change often; check each vendor’s own documentation before deciding.