- When creating an account for a client, it’s better to use their actual credentials so as not to have to deal with unresponsive Flutterwave support.
- Payment Links: You can create a payment link with a fixed amount or recurring and it’s valid until it’s deactivated. You can choose a subaccount onto which the payments through the link are settled.
- You can log cash transactions in the dashboard
- You can view your chargebacks.
- You can log refunds.
- Toggling back and forth between live and test mode does not require verification.
- You can create subaccounts and they can only be settled to through payment links.
- You can also create a Flutterwave virtual card.
- You should ideally request for the USD1000 single transaction limit and daily transaction limit to be modified at the creation of the account.
- When a payment is in RWF, that’s only when the MOMO payment option is available.
- Settlements will by default be made to the primary settlement account, to settle to other settlement accounts, you can use payment links whereby you can choose what percentage of the settlement goes to which account.
- A tenant agreement works as a proof of address
- Have all the required documentation from the merchant before you being the integration, this will save you a lot of time ahead. These documents depend on the merchant’s industry. They include: Travel license, tenant agreement, identification document for the business owner/representative with significant power in the business, bank statement, operations license, trading license, tax acknowledgement receipt, RDB incorporation and full Registration certificates, for a business representative you may need their contract to show their position in the company.
Learnings From Flutterwave integrations
When creating an account for a client, it’s better to use their actual credentials so as not to have to deal with unresponsive Flutterwave support.
