An eligible ecosystem service may cost more than a customer's available token balance. Allowing the remainder through another payment method sounds simple until the order changes. The design question is how one commercial purchase remains understandable when its funding comes from two separate instructions, each with its own evidence and timing.
Fix the allocation upfront
The checkout should record how much of the agreed invoice each method covers. That allocation gives the provider a single amount to reconcile while preserving the separate funding references. Asking the customer to make unrelated transfers without a common invoice creates uncertainty about when the order is fully funded and whether either payment can stand alone.
Decide what partial funding buys
A first payment might reserve an order, create a deposit or leave the purchase incomplete. Those outcomes should be explicit before funds move. A partially funded balance should not silently become an unrelated account credit. The customer needs to understand whether another instruction is required and what happens if they decide not to continue.
Preserve the refund arithmetic
If an order is reduced, the system needs a consistent allocation method for returning value across the original funding routes. Staff should not improvise based on whichever route is easiest that day. A record of the original split allows the refund explanation to match the invoice, including any disclosed conversion or processing treatment.
Choose simplicity deliberately
Mixed payment can increase completion but also increases reconciliation and support work. A provider might reasonably begin with one accepted route until those operations are dependable. ALFA's utility design should evaluate the whole order lifecycle before adding funding flexibility; the valuable feature is a purchase that remains clear when circumstances change, not merely another checkout option.
