Mixed Payment

Overview

A mixed payment settles one obligation using more than one payment method, currency, cryptocurrency, transaction, or source of funds. The system applies each component to the same order balance and completes the order only when the combined accepted value meets policy. It differs from a partial payment because the completed obligation can intentionally contain several payment components. For teams linking Mixed Payment to Crypto Payment Processor, operational acceptance requires exact asset and network identity, verified execution, a documented finality rule, and reconciliation with the linked order or account.

Important risks include double application, inconsistent exchange rates, incompatible refund methods, tax allocation errors, late components, and one component being reversed.

Systems should preserve order balance, each payment ID and method, amount, currency or asset, valuation, applied sequence, fees, settlement, and refund allocation.

Implementations should link Mixed Payment to Crypto Payment Processor and Payment Currency through auditable references. Although the records can share a customer or transaction, Mixed Payment retains its own authority, lifecycle, and recovery rules.

For Mixed Payment, pricing and asset identity must be reproducible. When Mixed Payment interacts with Crypto Payment Processor, records should retain the invoice or order, quote currency, pay asset, contract or native-asset identifier, network, decimals, rate source, rate timestamp, requested amount, received amount, fees, and settlement result. In the relationship between Mixed Payment and Payment Currency, this evidence supports customer support, reconciliation, tax reporting, refunds, and investigation of wrong-network or counterfeit-token payments.

For Mixed Payment, risk controls should be proportional to payment value and reversibility. When Mixed Payment interacts with Crypto Payment Processor, useful controls include allowlisted assets and networks, server-generated instructions, authenticated callbacks, independent transaction monitoring, confirmation or finality thresholds, duplicate detection, rate expiry, exception queues, and reviewed manual decisions. In the relationship between Mixed Payment and Payment Currency, merchant fulfillment policy should specify exactly which verified state permits delivery or account credit.