One approval.
One debit.[product]What you get
with Rivet
20+ countries.
Each leg on its local rail.
L. MoreauSEPA€ 3,850.00
S. PatelFPS£ 2,100.00
J. WhitakerACH$ 4,500.00
M. RossiOn-chain1,200 USDC
D. TremblayLocalC$ 3,000.00Waiting · over $10,000 threshold
Payroll, contractors, suppliersUpload a CSV or build the batch in the dashboard. Each leg goes out on the recipient’s local rail, or on-chain where there is none, and every leg is priced before you commit.
Four runs that turn an afternoon into one batch.
L. MoreauSEPA€ 3,850.00S. PatelFPS£ 2,100.00J. WhitakerACH$ 4,500.00A contractor in Toronto gets Canadian dollars in a Canadian bank; one in Lisbon gets euros over SEPA Instant. Same batch, same approval, same debit.
Every leg carries the reference you set, so payouts match invoices in your ledger without reading a bank statement.
A single batch can settle some legs over local rails and others in USDC, for the weekend, the holiday, or the corridor no rail reaches.
A failed leg is flagged on its own and retried without resubmitting the batch. Its money returns to your balance rather than sitting in limbo.
CSV, or straightfrom the dashboard.
Upload a file of beneficiaries and amounts, or pick them in the dashboard. Every recipient is validated before the batch can run.
Every leg pricedbefore you commit.
Each leg shows the rail it will take, its rate and its fee: Swift, SEPA, Faster Payments, a local rail or on-chain. You see the total before you commit.
One approval.One debit.
The approvers on your policy sign off the batch as a whole and the debit hits your account once. Legs go out over local rails and on-chain in parallel.
Local rails and on-chain legs go out in parallel, each with its own reference.
The approver signs off the batch, not each line. Set an amount above which a second or third approver is required; below it, batches go without a queue. A session PIN sits in front of the send.
Safe by design
Upload a CSV, review every leg, approve once.
No per-payment tiers. You see every fee before you send.
Upload a CSV of beneficiaries and amounts, or build the batch in the dashboard. Either way you see every leg, the rail it will take and what it costs before you commit. You see the total before you send.
That leg is flagged on its own and can be retried without resubmitting the batch. The legs that already succeeded are untouched, and the money for the failed one returns to your balance rather than sitting in limbo.
Yes. A single batch can settle some legs over local rails and others on-chain in USDC. That helps when a local rail is closed for the weekend, or does not reach where the recipient banks.
Whoever your policy says. Approval thresholds are configurable, with up to three approvers required above an amount you set. Below that, batches go without a queue, because a control everyone routes around is not a control.
In their own currency, into their own bank account, on the local rail that country uses. The recipient does not need a Rivet account, and does not need to understand how the money reached them.
It depends on the rail the leg takes. A Swift wire is $25.00, falling to $20.00 on Scale; SEPA is €5.00, falling to €3.00; Faster Payments is £3.00, falling to £2.00. Local payouts and on-chain legs are charged at your plan’s per-payout price: $2.00 on Starter, $1.00 on Growth, $0.50 on Scale. The FX margin applies on top only where a leg changes currency, and on-chain legs also carry the network fee. Every one of those is shown per leg before you confirm the batch.
Large enough for a normal payroll or supplier run. You do not enter recipients one by one. Upload the CSV and every leg is priced and routed before you commit. If your run is genuinely unusual in size, that is a scoping-call conversation rather than something to discover at the point of upload.