Log inGet started
Airwallex logo
Core API
Transactional FX
Back to home
OverviewUnderstanding Payments for PlatformsChoose your Payments for Platforms solution
Airwallex gateway
Airwallex payment gateway overviewProcess payments and manage funds
Collect payments directly
Collect payments on behalf of connected accounts
Manage funds split
Hold & convert funds

Collect payments directly

With this model, payments belong to the platform account solely. The platform account is responsible for Payments fees, refunds, and chargebacks. The fund will be split from the platform account to one or many connected accounts. It is recommended for the case where the platform directly interacts with end customers and manages daily transactions. Typical cases include marketplaces or on-demand service platforms.

You can specify which connected account to be associated with a given transaction by using the connected_account_id attribute. The below chart illustrates the process of a standard one-off 100 GBP payment in this model.

platform slipt to connected


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.

  1. Platform creates payment_intent with 100 GBP with connected account id
  1. Platform confirms payment_intent with normal request body
  1. Platform captures payment_intent with 100 GBP with normal request body
  1. Platform creates FundsSplit with 90 GBP where the source_id equals to payment_intent_id, the destination equals to connected account_id

In the case where funds need to be split into multiple connected accounts, the platform needs to create multiple FundsSplit to each connected account as a destination.

  1. Funds will be settled to all parties’ wallets based on split portion, where platform receives 5 GBP (5 GBP Airwallex fees being netted) and connected account receives 90 GBP as disbursement

If you want to create recurring payments in this model you also need to create a PaymentConsent with connected account id.