Use Moov transfer groups to chain a multi-party payment so each party sees the correct context of funds moving through them

Steps

1. Create the initial parent transfer normally (for example, customer to platform) via a POST to the transfers endpoint.
2. Create a child transfer with source.transferID set to the parent transfer's transferID (instead of a paymentMethodID) and a destination such as the service provider's payment method; the child transfer's amount must be less than or equal to the parent transfer's amount.
3. Track each transfer through the group lifecycle: a child transfer is queued until its preceding transfer reaches completed, then becomes pending while funds move, and finally completed.
4. Subscribe to the transfer.updated webhook event to be notified as each transfer in the group changes status.
5. Retrieve the groupID from any transfer's GET response — it equals the transferID of the most senior parent transfer — and call the list-transfers endpoint filtered by that groupID to retrieve every transfer in the chain.
6. Handle failure paths: if a transfer in the group fails, all subsequent not-yet-completed transfers are automatically canceled and funds remain at the destination of the last completed transfer; failed transfers can be retried.