Overview

When you send payments through Payments, you can use local payment networks in 15 currencies and corridors. These local routes deliver faster payments at lower cost compared to traditional international transfers.

Jump to

• Overview
• What are local payment routes?
• Who can use local payment routes?
• Where can I send local payments?
  • Supported SEPA recipient countries
• How much does it cost?
• Why does this matter?
• How is this different from SWIFT?
• Transaction limits
• How do I use local payment routes?
• Frequently Asked Questions
• Contact our Support Team

What are local payment routes?

Local payment routes use domestic banking networks within a country or region to move money, rather than routing through the international SWIFT system. When you make a payment in a supported currency to a supported country, Reap lets you select the local option if it's available for your recipient when creating a new payment.

Who can use local payment routes?

Sender country eligibility: Your business must be incorporated in one of these countries to access most local payment corridors:

Note: Hong Kong FPS and CHATS are available to all clients regardless of sender country.

If you're eligible, you'll see the local payment option when creating a payment to a supported corridor. There's no application process or additional setup required.

Where can I send local payments?

Payments currently supports local payment routes in these 15 corridors:

Supported SEPA recipient countries (54):

Being in the broader SEPA zone does not automatically guarantee support — availability is specific to Reap’s payment provider corridors.

How much does it cost?

Beyond fixed fees, you'll also see our standard variable transaction fee, typically 0.5% for Business Account clients. The cost savings add up quickly — for businesses making 50 payments monthly through local routes instead of SWIFT, you could save over USD 1,000 monthly on fixed fees alone.

Why does this matter?

Local payment routes offer three key advantages:

Speed

Many local networks operate around the clock with near real-time processing. SWIFT transfers can take up to 5 days.

Cost savings

The much lower fee for local payments compared to USD 25 for SWIFT creates meaningful savings at scale.

Higher success rates

Local networks use country-specific banking formats, which means fewer failed payments due to formatting errors.

How is this different from SWIFT?

SWIFT may route payments through multiple intermediary banks, adding time and fees. Local payment networks connect banks directly within a country or region with fewer intermediaries, standardised formats, and often real-time processing. The tradeoff is that local networks only work within their specific geography.

It is also important to note that SWIFT provides tracking capabilities, which local networks may not have as a result of their speed.

Transaction limits

Local corridors have transaction limits per payment, and they vary per corridor. For payments exceeding these limits, SWIFT remains the appropriate channel, and you can switch back when creating your payment.

How do I use local payment routes?

When you create a payment in the Reap dashboard, you'll see the available payment methods for your recipient. If a local route is supported, you'll see it listed alongside SWIFT with the associated fees displayed. The system automatically determines which routes are available based on the recipient's currency and country.

For existing recipients: Most existing recipients can use local routes right away. In some cases, particularly if you added the recipient before local routes became available, you may need to create a new recipient entry with the proper local bank details — such as an IBAN for SEPA, routing number for ACH, or other country-specific identifiers.

For new recipients: Simply provide the required local bank details when creating the recipient. The local payment option will appear automatically at checkout when available.

If you don't see a local option where you expect one, verify the recipient's bank details include the information required for local transfers in that country, or contact our support team.

Frequently Asked Questions

Why don't I see the local payment option for my recipient?

The local payment option only appears when the recipient's currency, country, and bank details are all supported for a local corridor. If it's not showing, check that the recipient's bank details include the required local format. If the details are correct and the option still doesn't appear, the recipient's country may not be supported for local payments on that corridor.

What bank details do I need for EUR SEPA payments?

An IBAN is required for all EUR local (SEPA) payments. A BIC/SWIFT code is optional but recommended for accurate routing. The recipient's bank account must be registered in one of the 54 supported SEPA recipient countries.

My recipient is in a SEPA member country. Why isn't it supported?

Reap's SEPA coverage is based on our payment provider's approved country list, which may not include every country in the broader SEPA zone. If a country does not appear in the supported list, it is not currently available — regardless of whether it is a formal SEPA member. You can still send EUR via SWIFT to unsupported countries.

What happens if my payment exceeds the transaction limit for a local corridor?

If your payment amount exceeds the limit for the local corridor, SWIFT will be the appropriate channel. Transaction limits vary per corridor, so check the available options at the time of payment creation.

Can I switch between local and SWIFT for the same recipient?

Yes. When creating a payment, you'll see both local and SWIFT options listed with their associated fees where both are available.

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.