Get paid.
Stay in control.

You install recv.fund on a Linux server you control. It gives you a dashboard, a checkout page and an API. Each customer has a permanent deposit address, and every payment is a plain transfer from the customer's wallet to that address; it does not pass through any recv.fund contract or program. Your server watches the chain and marks the payment as paid. Your server then sweeps the deposit address, and your merchant contract (Robinhood Chain) or the recv.fund program (Solana) sends the funds to the settlement wallet you registered.

We never hold funds and we never run your server. Customer payments go straight to deposit addresses that belong to your registration, not to a recv.fund contract. When a deposit address is swept, the contract or program sends funds only to your registered settlement wallet and to the fee collector recorded in your registration; neither has a function that sends funds anywhere else. Only your own admin wallet can change the settlement wallet.

Your own hot wallet, one per chain family, encrypted at rest. It is registered on-chain as your sweeper: it can start sweeps to your settlement wallet, pays their network fees and sends payouts you approve. It cannot change the settlement wallet. Your admin wallet signs registration and settings changes from your browser; the server never receives its key. Deposit addresses are derived from your merchant contract or the program, so no deposit private key exists.

One fee, taken only when you sweep a deposit address to your settlement wallet. Customer payments carry no fee: the full amount arrives at the deposit address. The dashboard shows the rate before you sign the registration. The rate is then fixed in your own on-chain record and is capped at 2% by the contracts and the program. If the fee collector cannot receive a fee, that fee goes to your settlement wallet instead, so the fee collector does not block a sweep. No subscription, no setup fee. You pay for your own server and network fees.

Not for an existing registration. The rate and the fee collector are copied into your merchant contract (Robinhood Chain) or merchant account (Solana) when you register, and no function or instruction changes them afterwards. recv.fund can change the terms only for registrations made after the change. The Robinhood Chain contracts have no upgrade mechanism. The Solana program on devnet can still be upgraded by recv.fund, and an upgrade could replace these rules; your server refuses a Solana mainnet program that still has an upgrade authority.

Robinhood Chain (USDG, ETH) and Solana (USDC, USDT, SOL). The contracts and the program are deployed on Robinhood Chain testnet and Solana devnet only. They are not yet deployed on mainnet.

No. Your install talks to each chain over RPC. Public endpoints work; you can add your own node or a paid provider in the dashboard and mark one as preferred.

Not by us. There is no account with us, no signup and nothing we host that your install depends on. The contracts and the program have no pause or freeze function. Your own admin wallet can mark your registration inactive; your server then stops offering checkout. The flag has no effect on-chain, so it does not stop sweeps of funds at a deposit address to your settlement wallet. On Solana devnet, the upgrade note above applies.

No. The server and dashboard are proprietary, and the contract and program source repositories are not public. The source of the Robinhood Chain testnet factory contract is verified on the chain's Blockscout explorer. Your server checks the deployed code of the Robinhood Chain contracts and the Solana program against hashes pinned in its release.