Manage split funds flow

By default, split funds will follow the standard settlement mode, where the funds will be batched up once we finish reconciliation on the source payment intent. It will be settled to the destination account’s wallet following the settlement time settings on the destination account.

In some cases, you may want the destination account to receive part of the funds in a more flexible manner. For example, marketplace platforms might have agreed with their sellers to only receive the funds after the end customer has confirmed the goods or services have been delivered. In this case, you can change the FundsSplit into a manual-release mode.

Manual-release is an option that could be applied with both processing models. Here is an example of when payment is owned by the platform account. The platform creates a 100 GBP payment and 2 corresponding splits to different connected accounts and would like to manually release the funds at different times.

1. After the 100 GBP payment has been captured, Platform creates a FundSplit with the amount of 40 GBP to Connected Account 01 and another FundSplit with the amount of 30 GBP to Connected Account 02. In the request body of FundsSplit, Platform specifies the value of the parameter auto_release as false.

   $  curl --request POST \
   >  'https://pci-api-demo.airwallex.com/api/v1/pa/funds_splits/create' \
   >  -H 'Content-Type: application/json' \
   >  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q' \
   >  -d '{ 
    "request_id": "ee939540-3203-4a2c-9172-89a566485dd9",
    "source_id":  "int_e65tkXCSzJrsMpTrzoFrjaau53",
    "source_type":"PAYMENT_INTENT",
    "amount": 40, 
    "destination":"acct_ij2YyjhFNv-BGPsjqHuI3w",
    "auto_release": false, 
    "type": "disbursement" 
    "metadata": { 
       "reason": "disbursement to seller A"
    }
   }'

   $  curl --request POST \
   >  'https://pci-api-demo.airwallex.com/api/v1/pa/funds_splits/create' \
   >  -H 'Content-Type: application/json' \
   >  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q' \
   >  -d '{ 
    "request_id": "ee939540-3203-4a2c-9172-89a566485dd9",
    "source_id":  "int_e65tkXCSzJrsMpTrzoFrjaau53",
    "source_type":"PAYMENT_INTENT",
    "amount": 30, 
    "destination":"acct_aD5rChdqMoCkSn3WseuKLw",
    "auto_release": false, 
    "type": "disbursement" 
    "metadata": { 
       "reason": "disbursement to seller B"
    }
   }'

2. After the payment has been reconciled, the platform will receive 30 GBP (netter of Airwallex fees, in this example 5 GBP) and the connected account will receive 70 GBP

3. When the Platform confirms that the Connected Account 01 has fulfilled its part of the service, it must release the outstanding 40 GBP through FundsSplit with the specified split id

   $  curl --request POST \
   >  'https://pci-api-demo.airwallex.com/api/v1/pa/funds_splits/spt_hkpdg99czg1gr7y49mo/release \
   >  -H 'Content-Type: application/json' \
   >  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q' \
   >  -d '{ 
    "request_id": "ee939540-3203-4a2c-9172-89a566485dd9",
   }'

4. The 40 GBP split fund will be settled to Connected Account 01 in the following settlement cycle

5. The same logic applies to Connected Account 02, the Platform must release the funds with the specific split id when it confirms that the Connected Account 02 has performed the required services

   $  curl --request POST \
   >  'https://pci-api-demo.airwallex.com/api/v1/pa/funds_splits/spt_hkpdpgsz7g1gqpqabao/release \
   >  -H 'Content-Type: application/json' \
   >  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q' \
   >  -d '{ 
    "request_id": "ee939540-3203-4a2c-9172-89a566485dd9",
   }'