Business Account The unified account layer for stablecoin-enabled businesses
Learn more
Embedded Finance Launch branded financial products on Reap's infrastructure, one API integration
Learn more
compliance
Agentic Payments Agentic spends on any merchant, anywhere. Agent-native checkout live today.Explore
One stack, direct or embedded.See pricing

Let your users collect payments. Reconciled automatically.

Add pay-ins to your platform: give each user a dedicated virtual account to receive payments. Let Reap match, convert & credit every transfer. No manual reconciliation.

VIRTUAL ACCOUNTS

Dedicated virtual accounts per user, per currency.

Building payment collections yourself means provisioning account numbers, attributing every transfer and reconciling it back to the right user. Reap handles it for you.
Infographic placeholder

Unique account numbers

Each of your users gets their own funding address: a dedicated virtual account number per currency and network. Incoming funds are attributed to the right user automatically.

Infographic placeholder

One address, unlimited collections

Once a funding address is active, it can receive funds indefinitely, across as many collections as you need.

Infographic placeholder

Works across the platform

The same virtual accounts are used for fiat top-ups across Reap. One account number, multiple use cases.

PAYMENT LINKS

We create the payment link. Your users get paid.

Create a collection against an invoice and Reap returns a hosted payment link with everything the payer needs.

Structured around invoices
Set the amount, currency and registered payer to create a payment link. The hosted link shows the payer the bank account, transfer reference and amount to send.
No payment pages to build
The hosted payment page handles everything the payer needs to complete the transfer. Incoming funds are tied to the right collection automatically.
Payers pay in their own currency
Payers can send in their local currency. Reap handles the FX and credits your user in their preferred receiving currency.

AUTOMATED PAYMENT RECONCILIATION

Every transfer matched. Every balance right.

Infographic placeholder

Funds matched on arrival

When funds land, Reap matches them to the collection by transfer reference and credits the right user in their configured currency.

Infographic placeholder

Partial payments tracked

If the payer sends less than the invoice amount, the collection moves to Partially Received and stays open to track outstanding amounts.

Infographic placeholder

Overpayments protected

If a payer sends more than the invoiced amount, Reap refunds the full amount instead of crediting it.

MORE THAN COLLECTIONS

More than collections.
The whole money-movement stack.

Send, receive and convert value the way your platform needs — all on the same integration, with the same operational support.

Payments

Stablecoin-funded fiat payouts across 45+ corridors.

CHECK IT OUT

On-ramps

Fiat-to-stablecoin conversion.

CHECK IT OUT

Off-ramps

Stablecoin-to-fiat withdrawals.

CHECK IT OUT

CARD ISSUING

Issuing cards? We have that too.

Beyond money movement, Reap offers card issuing and agentic payments – the full stack to power your product roadmap.

Card Issuing

Issue branded cards to your users.

CHECK IT OUT

Agentic Payments

Enable agentic spending for AI-driven use cases.

CHECK IT OUT

One platform

Same team, same integration you're already using for collections.

USE CASES

Collection flows built on Reap

Whether your users are invoicing their first client or reconciling thousands of transfers, the work underneath is the same — and it's the part nobody wants to build twice.

01 For

B2B platforms collecting on behalf of users

Your users need to collect from their own clients: against invoices, for services rendered, or at project milestones. Each user gets a dedicated funding address. When a client needs to pay, you create a collection and share the hosted payment link. The client transfers, Reap attributes the funds, and the user's balance updates automatically. You see outstanding receivables across every account in real time.

01 For

Pre-funding accounts for outbound payments

You use Reap's Payments module and your users need to deposit funds before they can send payments. Funding addresses give each user a dedicated account for fiat deposits. Once funds land and are attributed, they're available for outbound payments straight away, so users who prefer fiat never have to touch a crypto wallet.

01 For

01 For

01 For

HOW IT WORKS

Get started in 4 steps

TALK TO OUR TEAM
01

Talk to our team

We scope your use case, user base and target markets, and agree the best path forward.
02

Integrate

Build against the sandbox. Create accounts for your users, provision funding addresses and register payers.
03

Test the full flow

Create invoice collections, share payment links and run the full lifecycle — funding address creation, partial receipts, expiry and webhooks — in the sandbox.
04

Go live

Your users start receiving funds. Reap attributes, converts and reconciles automatically, with a webhook at every step.

What you do vs. what Reap does

You
Reap
Choose assets and pricing
Authorises spend against available balance
Maintain user balances (deposits/withdrawals/repayments)
Clears, reverses, and settles transactions
Fund the master collateral account
Holds the master collateral account
Keep custody and the user relationship
Polls your pricing feed for dynamic-rate assets
Applies your balance updates atomically
FAQ

Questions platforms ask before embedding collections

01
What is Reap API's Collections product?
+
Reap API's Collections product is a payment collection API that adds pay-ins to your platform, so your users receive and reconcile payments in your product. Each user gets a dedicated virtual account, you create collections against invoices and share a hosted payment link, and Reap matches, converts and credits every incoming transfer. Partial payments are tracked and every receipt fires a webhook.
02
Can a collection be paid in instalments?
+
Yes. Each partial receipt moves the collection to Partially Received and fires a webhook with the updated total. The collection completes automatically once the invoice amount is covered.
03
What happens if the payer sends too much?
+
Reap refunds the full amount. Overpayments aren't silently credited.
04
Can payers pay in a different currency?
+
Yes. Payers can send in their local currency. Reap handles the FX and credits your user in their preferred receiving currency.
05
Can one funding address be used for more than one collection?
+
Yes. Once active, a funding address receives funds indefinitely across multiple collections. Requesting the same currency and network again returns the existing address.
06
Can I test collections in the sandbox?
+
Yes. Simulation endpoints let you test fiat deposits, funding address status changes and collection status updates end to end.
07
What's the difference between Collections and On-ramp?
+
Collections is for your users receiving money from their own clients, matched to invoices and credited in their chosen currency. On-ramp is for your users depositing their own local currency from their bank and receiving stablecoins.
Get Started

Start collecting on Reap

NEW: Now supporting stablecoin card programs across 100+ markets Learn more