Building a Marketplace on Medusa: Vendors, Splits and Payouts
Multi-vendor commerce means splitting one customer order into several vendor orders, and moving money to people who are not you. The model and the money mechanics.
Articles tagged Payments — hands-on notes from the commerce builds we ship.
Multi-vendor commerce means splitting one customer order into several vendor orders, and moving money to people who are not you. The model and the money mechanics.
Recurring billing is a scheduling problem with money attached. The data model, the renewal workflow, and the failure handling that determines involuntary churn.
The four capabilities that separate B2B from DTC, modelled as Medusa modules and workflows — with the data model that makes approvals work.
Regions carry currency, tax, payment methods and shipping. How to model international selling without accidentally creating twelve stores.
UPI, netbanking, RuPay and the mandate rules that make Indian payments their own discipline. Integrating Razorpay with Medusa properly.
Adding PayPal alongside cards, wiring the JS SDK buttons into a Next.js checkout, and the dispute and webhook behaviour that differs from a card processor.
The provider interface method by method, a working implementation, and the idempotency and webhook details that separate a demo from something you can take money with.
Configuring the Stripe module, wiring Payment Elements into a Next.js checkout, and the webhook and 3D Secure details that decide whether payments reconcile.
Address, shipping, payment session, complete. The four stages of a Medusa checkout, the state machine underneath, and the failure modes that cost orders.
How Medusa's payment abstraction works, why running two providers is easier than you think, and the authorise-versus-capture decision that determines your refund story.