Product: Reap API (Payment API)
Who this is for: What the Payments API is, whether your business can use it, where you can send money, how funding works, and how to get started.
What you will learn: Businesses evaluating whether the Payments API fits their use case, and teams preparing to integrate.
Overview
Reap's Payments API lets a business embed global payment functionality directly into its own platform, rather than creating each payment by hand.
The type of payments program you set up determines how your account is created and how funds flow through it. Every program can use the corridors and funding methods described below.
Can I use the Payments API?
Three rules apply to every payments program, without exception:
- Senders must be businesses. Individuals cannot send payments.
- The sender and recipient cannot be the same legal entity. First-party payments, meaning moving money to yourself, are not supported.
- Only the account owner can fund the account. Funds must arrive from the verified entity (Managed account) that owns it, not from a third party.
All three apply to the ultimate sender and beneficiary, not only the parties named on a payment. None of them can be worked around, so check them against your use case before anything else.
What can I pay for?
Two use cases are supported:
- Purchase of goods and services. The sender has bought a good or service from the recipient.
- Inter-company transfers. The sender and recipient are legally associated entities, such as a holding company funding a subsidiary.
Payments in both cases must be supported by documentation, which Reap can request at any time. Build that into your process from the start rather than retrofitting it later.
What can I not pay for?
Restricted categories include cash disbursements, foreign currency and money orders, dating and escort services, gambling and betting, bail and bond payments, debt collection, goods infringing intellectual property, cash-intensive businesses without oversight, deceptive financial services, weapons and hazardous materials, adult entertainment, unregistered charities, and pharmaceuticals.
Payments are also restricted where either the sender or the recipient is in a restricted jurisdiction. Reap publishes the current list, which covers 29 countries.
⚠️ Neither list is exhaustive, and both change over time. Check the Restricted Activities documentation for the authoritative version rather than relying on a summary. If you are unsure whether a use case qualifies, ask before building for it.
Where can I send money?
A corridor is a supported combination of currency, payment network and destination, such as SGD over FAST into Singapore. Two kinds are supported:
- SWIFT — 26 major currencies, sent globally
- Local networks — 18 corridors settling on a country's own payment rail, across Asia, Europe, North America, the Middle East and Latin America
Some corridors are conditionally available and need a conversation with the Reap team first. Any corridor may also require additional approval, or be unavailable because of the restricted jurisdictions above.
Supported corridors change as Reap adds more, so check the current list rather than working from a saved copy. There are two places to look, and they answer different questions:
- Making Payments lists every currency, network and destination Reap supports.
- The corridors endpoint, available once your account is set up, returns the corridors enabled for your account specifically, with the minimum and maximum transaction amount for each.
If the corridor you need is not supported, tell the Reap team. What gets added next is driven by client demand.
How do I fund my account?
Payments are funded with stablecoins. Your account is issued its own dedicated address on each supported network:
- USDC on Ethereum, Polygon PoS and Solana
- USDT on Ethereum, Polygon PoS, Tron and Solana
You do not need funds in place to create a payment. One created without sufficient balance waits in an Awaiting Funds state, and the quoted price is held for approximately one day. That lets you queue payments ahead of a funding transfer, though the one-day quote window is worth designing around.
⚠️ Three things commonly trip up a first transfer
- Bridged tokens are not supported. Only the network-native asset is credited. Bridged USDC on Polygon, for example, will not be.
- A Solana address takes a moment to create. The first time you add funds via Solana, generating your dedicated wallet takes two to four minutes. After that it appears instantly.
- Only the account owner can fund the account. A transfer from any other entity will not be credited.
Every deposit is screened before being credited, so funds usually appear within a few minutes rather than instantly. If a valid deposit has not been attributed after 10 minutes, contact Reap.
How do I get started?
Access starts with a conversation rather than a signup form:
- Align on the program. The type of payments program you want determines how your account is created and how funds flow through it.
- Agree commercial terms.
- Integrate and launch. Once the program and commercials are aligned, Reap implements the integration with your team and launches your program.
For more information, see Getting Started.
Frequently Asked Questions
We want to move money between our own group companies. Is that supported?
It depends on whether they are the same legal entity. Transfers between legally associated entities, such as a holding company funding a subsidiary, are supported as inter-company transfers. Moving money between accounts belonging to the same legal entity is not, and that applies to the ultimate sender and beneficiary rather than only the parties named on the payment.
Can an individual send payments through the Payments API?
No. Every sender must be a legally established business, across all payments programs.
Do I need funds in the account before I can create a payment?
No. A payment created without sufficient balance waits in an Awaiting Funds state, and the quote is held for approximately one day. This lets you queue payments ahead of a funding transfer, but the one-day window is worth designing around.
What if the currency or country I need isn't supported?
Tell the Reap team. Corridor coverage expands based on client demand, and some corridors are conditionally available on request.
Contact our Support Team
If you have questions or need assistance, contact our support team via the Live Chat in the Reap Dashboard (bottom right corner) or email us at hello@reap.global
For more information, visit Know who to talk to at Reap.