Defining Your Program

Overview

We currently support two types of payments programs:

1. Payments for yourself (single or multiple entities)
2. Payments on behalf of your customers

All payments programs have access to our payment capabilities and must adhere to our allowed and restricted activities.

Payments for yourself

Our Reap Dashboard clients typically use their Reap Pay dashboard to manage payments they are making for themselves (e.g. paying a contractor or vendor). With the upcoming launch of our Global View feature, if you have multiple onboarded entities with accounts in our system, you will be able to log-in with one single email and access all of your entities' dashboards.

However, we recognize that certain clients may want to manage their payments more programmatically, especially if complex financial process are run by in-house systems and multiple entities are involved. Our Payments API can definitely help here!

If this situation applies to you, please reach out to us to align on an implementation plan - as the Payments API is in beta, there are some functionalities not yet available via API that do exist in Reap Pay. Good news is that no additional KYB is needed for existing accounts and that all accounts will be visible under the Global View single log-in.

Payments on behalf of your customers

Helping you make payments on behalf of others besides yourself (e.g. customers of your platform) is the primary service offered by our Payments-as-a-Service (PaaS) business line.

While you would still integrate into the same Payments API as a Reap dashboard client looking to streamline their operations, given the nature of on-behalf-payments there are additional compliance requirements and separate commercials. This involves creating a Master Account (which we also call a Manager Account), and then create a Managed Account for each of your customers whom you are making payments on behalf of. You can read more about the concept of Manager vs Managed Account in our Account Management section.