With ReadyRemit you'll be able to integrate cross-border disbursement or remittance in a matter of weeks. This guide will help you get started by identifying your integration type and choosing the right integration guide. If you have any questions, please get in touch with the ReadyRemit Integrations Team.

1. B2C vs C2C

The first question you will need to answer is whether the ReadyRemit Transfers will be classified as Business-to-Consumer (B2C) or Consumer-to-Consumer (C2C) transactions. The key differentiator between these use cases is the source of the funds.

In the Business to Consumer (or B2C) use case, funds originate from your company's account and are disbursed to your end-users. In this case the Sender entity in ReadyRemit is your company and the Recipient entities in are your users.

In the Consumer to Consumer (or C2C) use case, funds originate with your end users and are sent to either themselves or a friend or family member. In this case the Sender entity in ReadyRemit is your user and the Recipient entities represent the user sending money to themselves or another person.

Based on your identified transfer type, certain compliance requirements / integration points are required.

2. API vs SDK

📘

B2C

If your identified transfer type is B2C, only API integrations are supported.

In an SDK integration, several API endpoints are still required for integration from your server but the ReadyRemit SDK handles 90% of the transfer flow. This type of integration can dramatically reduce time-to-market. Some requirements to be eligible for an SDK integration:

• Your transfer types will be classified as consumer-to-consumer (C2C).
• You provide your users a mobile application and or web application where the ReadyRemit SDK can be initiated.
• You don't require any changes to the remittance flow other than cosmetic.

If an SDK integration isn't possible, an API-only integration will give you complete control over the remittance flow for your users.