Step 1: Generate your API key
Head over to dashboard.lumx.io. Once logged in, generate a new API key and store it securely. See Authentication for details.Step 2: Create your marketplace partner fee
Configure once how much of every transaction the marketplace keeps and where the fee should be sent. ThewalletAddress is the marketplace’s own wallet. Rates are in basis points (e.g., "500" = 5%).
Request
Response
id. You’ll reference it on every transaction. See Partner Fees for the full schema.
Step 3: Onboard each seller
For each seller that lists on your marketplace, create a customer: individual for sole proprietors, business for incorporated sellers. They must accept Lumx’s terms of service (POST /customers/{id}/tos) and complete identity verification before they can receive funds.
If your sellers will receive USD payouts from external platforms (Scenario B), provision a USD virtual account on the same call by passing accounts: ["USD"]. Sellers who only sell through your local checkout (Scenario A) don’t need an account; incoming on-ramps credit their wallet directly.
Request
Scenario A: local checkout for global sellers
Use this flow when your marketplace runs the checkout itself and buyers pay you in their local currency. PIX (BRL) and SPEI (MXN) are the two realistic rails: instant, push-based, and the way buyers already expect to pay online in those countries.Step 4A: Create a checkout for each sale
When a buyer is ready to pay a seller, create an on-ramp transaction on the seller’s behalf, referencing yourpartnerFeeId. The response includes the payment details (a PIX brCode or a SPEI CLABE) which you display in your checkout flow.
Use purpose: "TRADE_TRANSACTIONS" for goods and services sales.
- PIX (BRL)
- SPEI (MXN)
Request
Step 5A: Settle the buyer payment
When the buyer pays the returned instructions, the transaction follows this lifecycle:AWAITING_FUNDS → TRANSFERRING_FIAT → TRADING → TRANSFERRING_STABLECOIN → SUCCESS
On SUCCESS, the seller’s wallet receives stablecoin net of your fee, and your marketplace wallet receives the partner fee, both in the same flow, no extra API call needed.
Subscribe to onramp.success and onramp.failed webhooks to mark the order as paid in your marketplace and unlock fulfillment. See Webhooks.
Scenario B: USD collection from external platforms
Use this flow when sellers earn on platforms outside your marketplace (Amazon, Shopify, Etsy, foreign clients on wire) and your product gives them a USD virtual account (issued by a Lumx banking partner) to receive those payouts. Once the wallet is funded, the seller off-ramps to their local currency.Step 4B: Create an autoconversion rule for the seller’s USD account
Once the seller’s USD account isACTIVE, create an autoconversion rule for it, referencing your partnerFeeId. You do this once per seller: the response’s sourceDepositInfo carries the ACH, Fedwire, and SWIFT details the seller pastes into Amazon, Shopify, or any other payer’s payout settings. Every payout that lands is converted to stablecoin and credited to the seller’s wallet net of your fee, whatever the amount.
Request
onramp.success and onramp.failed to know when payouts land or fail. For the response, the deposit details per rail, and when to create a one-off on-ramp instead, see Global accounts.
Step 6: Settle to the seller’s destination
This step applies to both scenarios. Before a seller can cash out, register their own destination withholder.relationship: "SELF". Local sellers receive in their home currency; sellers in jurisdictions Lumx doesn’t settle in receive USD via SWIFT.
Sellers in jurisdictions outside Lumx’s settlement currencies (e.g., Hong Kong, Singapore) receive USD via SWIFT into their local USD-denominated account. See Coverage for the full list of supported settlement currencies and rails.
- PIX (BRL)
- SPEI (MXN)
- ACH (USD)
- SEPA (EUR)
- FPS (GBP)
- SWIFT (international, USD)
Request
purpose: "PERSONAL_ACCOUNT" since the seller is moving funds to their own account. Include partnerFeeId only if your marketplace charges a separate withdrawal fee; in Scenario A the platform fee was already collected on the on-ramp, so applying it again here would double-charge the seller.
Request
Related resources
Partner Fees
Configure platform fees on on-ramp and off-ramp transactions.
Transactions
On-ramp lifecycle, purpose codes and rails.
Exchange Rates
Lock FX rates for stablecoin-priced catalogs.
Destinations
Seller withdrawal destinations.