Mixed Basket Payments

What Are Mixed Basket Payments?

Mixed basket payments describe transactions where a single purchase is funded using more than one payment instrument simultaneously. A consumer pays €120 of a €150 order with a credit card and covers the remainder with a gift voucher. A corporate buyer settles part of an invoice against a company card and the balance against an approved credit line. A marketplace customer combines loyalty points, a discount code, and a stored card in a single checkout session.

While most visible in consumer retail, mixed baskets are equally prevalent in B2B procurement (partial prepayment plus net payment terms), marketplace platforms (sellers may accept different payment methods), and corporate travel (company card, employee out-of-pocket, and travel allowance combined in one booking).

Technical Challenges of Mixed Basket Orchestration

Split Authorisation and Atomic State Management

Orchestrating a mixed basket requires firing multiple authorisation requests—one per instrument—and managing the combined result atomically. If the gift card authorisation succeeds but the card authorisation is declined, the payment system must either release the gift card hold or present the customer with an alternative. This rollback and retry logic must be handled consistently across asynchronous responses from different provider systems, without creating orphaned holds or partial charges.

Multi-Provider Settlement and Reconciliation

Each instrument in a mixed basket typically settles through a different provider: the card through an acquirer, the voucher through a loyalty platform, the BNPL product through a consumer credit provider. Reconciliation must correlate multiple partial settlement events back to a single internal order identifier. Without a normalised event layer, this reconciliation multiplies in complexity with every additional instrument type.

Regulatory and PCI Scope Considerations

Different instruments carry different regulatory obligations. Card payments fall under PCI DSS; BNPL products may require consumer credit licensing checks; stored value vouchers may be subject to e-money regulation. The payment infrastructure layer must apply the correct compliance controls per instrument within the same checkout flow.

How Hellgate Hub Handles Mixed Basket Payments

Hub, Hellgate's composable orchestration engine, natively supports split authorisation flows. Payment managers configure the instrument sequence, authorisation thresholds, and fallback logic in Hub's flow builder—without writing custom code. Link's PSP abstraction layer routes each instrument to its appropriate provider through a consistent API surface.

Pulse normalises the resulting multi-leg settlement events into a unified order view per transaction, making mixed basket reconciliation as straightforward as single-instrument settlement. Guardian ensures any card instrument in the basket is tokenised at capture and stored under a portable credential, independent of which acquirer processes the card leg.