A marketplace payment looks simple to the buyer. Behind the checkout, the platform must account for the seller’s proceeds, its own commission, delivery charges and any later refund or dispute.
Each movement has an owner, a timing requirement and an accounting consequence. A system designed around one buyer and one merchant may not cover that wider flow without additional tools.
Timing is an early challenge. Sellers may expect payment before delivery is confirmed, while buyers expect protection if an order goes wrong. The platform needs clear release rules and a way to deal with exceptions.
Seller onboarding creates a separate operational task. The payment arrangement must establish who verifies sellers, which information is required and what happens when an account cannot receive funds. At scale, unresolved onboarding issues can become payout and support problems.
Refunds after payout require particular care. If the seller has already received the money, the system must determine how the refund is funded and whether the amount can be recovered. That cannot be left to an improvised spreadsheet when a customer asks for their money back.
Disputes create another division of responsibility. The platform may receive the claim while the seller holds the delivery records and customer correspondence. Evidence needs to move between them within the relevant deadlines.
Gordeon‘s positioning around complex merchant requirements is relevant to these questions. For a marketplace, the payment specification should include payout logic and reconciliation, rather than stop at accepting the buyer’s payment.
Cross-border sellers add currency conversion, settlement and local availability to the design. The marketplace should be explicit about who bears conversion costs and what a seller will receive.
Holding or moving funds for third parties also requires a properly structured payment arrangement. Responsibilities depend on the markets and the services involved; a provider relationship does not automatically settle every obligation for the platform.
The most useful starting point is to map a transaction from purchase through payout, refund and dispute. For each step, identify the responsible party, the record created and the source of funds. If those answers are unclear, the marketplace is carrying an operational problem that checkout performance alone cannot solve.
Written in partnership with Tom White
