Collect payments on behalf of connected accounts
With this model, payments belong to your connected account instead of you as the platform. The connected account is responsible for Payments fees, refunds, and chargebacks. The fund will be split from a connected account to a platform account. It is recommended for the case where the connected account directly interacts with end customers and manages daily transactions, while the platform has limited engagement in every transaction. Typical case includes SaaS platforms.
In this model, the platform will submit all the payments on behalf of the connected account to Airwallex. In order to indicate this relation, you need to specify the account ID of the connected account with the
The below chart illustrates the process of a standard one-off 100 GBP payment in this model.
In the case of Hosted Payment Page/Embedded Fields/Drop-in/Mobile Integration, platform can bypass step 2&3 but needs to create the
FundsSplit request after receiving notifications that the payment is successfully captured.
- Platform creates
payment_intentwith 100 GBP on behalf of connected account with id
- Platform confirms
payment_intenton behalf of connected account
- Platform captures
payment_intentwith 100 GBP on behalf of connected account (you can also skip this process by choosing auto capture)
- Platform creates
FundsSplitwith 10 GBP on behalf of connected account, where the
destinationequals to platform account’s own
account_id. Platform can use
metadatato record values that help better recognition of each split
- Funds will be settled to both parties’ wallets based on split portion, where platform receives 10 GBP as commission and connected account receives 85 GBP (5 GBP Airwallex fees being netted)
If you want to create recurring payments in this model you also need to create and verify a
PaymentConsent on behalf of connected account.