Allow you to submit a payment with multiple legs to the platform. The payments are processed asynchronously and must contain at least two legs, but no more than 20. The payload contains debits and credits lists. These lists include legs that follow the requirements of credit and debit objects in the Post payment endpoint. For information about multi-leg payments, refer to the Multi-leg payments guide. NOTES:

• To find the correct reason IDs, refer to the List account status reasons endpoint.
• This endpoint does not support forced transfers from an earmark balance.
• For error handling, see Error handling mechanism in Payment overview.
• Processing sequence: Debit legs are always processed before credit legs. Within each group, the sequence is not guaranteed, and the order of execution among debits or among credits is non-deterministic.

Each leg generates the following events:

• Platform authorization created
• If flex controls are configured, a Flex control evaluated event is triggered. Additionally, the following events are generated for multi-leg payments:
• Multi-leg payment lifecycle created
• Multi-leg payment lifecycle status changed See Data and reporting for more information about events and setting up event notifications.