When using split payments, each payment authorization for a gateway integrations is managed individually using the webhook appropriate for that gateway, such as the Generic Payment webhook or the Credit Card Payment webhook. Payment authorizations for built-in gateways such as CyberSource are managed internally. A separate call is made for each payment group.
Webhooks that include payment data for entire orders, however, must handle multiple payment groups. The request bodies of the following webhooks can include multiple payment groups, one for each payment method instance used in the order:
Order Submit
Order Submit for Non-PCI Compliant Target Systems
Cart Idle
External Price Validation
Return Request Update
Return Request Update for Non-PCI Compliant Target Systems