Lumino lets a software platform or marketplace offer payments to its users without building or registering a payments operation of its own. Your users are onboarded as merchants, pay-ins happen through embedded checkout or hosted fields in your product, payouts to those sub-merchants are handled through Lumino’s processing partners, and you see the whole portfolio in one report.
Your users apply as merchants through a guided flow, with underwriting carried out through Lumino’s partners. It follows the approach in faster merchant onboarding.
Scoping and implementation
The enterprise team maps your users and flows of funds with you, and professional services plans the integration and the onboarding of your first cohorts.
In practice
HowdoplatformsandmarketplacesuseLumino?
01
Adding payments to vertical software
A software platform for salons wants owners to take card payments without leaving the booking screen. The team scopes the flows of funds with Lumino and embeds hosted fields so card data stays on the processing side. Each salon owner then completes a merchant application from inside the product, and the review is carried out on the processing side.
A marketplace for local services takes one payment from a buyer and owes most of it to the seller. With Lumino, each seller is onboarded as a sub-merchant, payouts to sellers are handled through Lumino’s processing partners, and how the marketplace’s commission is collected is agreed during scoping. Deposits and batches across all sellers appear in one report.
A reseller with a growing book of merchants knows that a few accounts can affect the standing of the whole portfolio. New merchants go through an onboarding review, dispute and VAMP ratios are followed for every MID in one view, and accounts trending the wrong way are flagged with time to act.
We map your volume, channels and entities first, then put a proposal against your current costs.
Responsibilities in writing
Which party handles card data, underwriting and compliance is set out in the Trust Center and in your agreement.
Moved in stages
Locations, brands or merchant groups move in an order you agree to, not all at once.
A direct line to the enterprise team
Start with contact sales and tell us what you are moving. We reply with the next steps.
FAQ
Platforms&Marketplaces:questions,answered
What are embedded payments?
Embedded payments are card payments taken inside a software product, so its users do not have to send customers to a separate provider. The checkout sits in the platform’s interface, each user has a merchant account behind it, and a payments partner carries the regulated side of processing. With Lumino this is done through embedded checkout or hosted fields.
What is the difference between embedded payments and becoming a PayFac?
A payment facilitator registers with the card networks and is responsible for its sub-merchants. Embedded payments through a partner gives the same in-product experience while the partner and its processors carry the regulated role.
Who is the merchant of record?
It depends on the model agreed for your platform. In most partner-led setups each business on your platform is the merchant for its own sales. See merchant of record.
How does a platform engagement with Lumino start?
It starts with a scoping conversation with the enterprise team. Share your volume, sales channels, current processor and timeline through contact sales, and we work out who your users are, how money should move between them and which parts belong in your product. A proposal and an implementation plan follow from that conversation.
How does a platform earn from payments?
Typically through a share of processing revenue on the volume its users process. Terms are agreed case by case rather than published.
How is pricing set for a platform?
Pricing is scoped to your volume and setup, so no platform figures are published. The enterprise team sets out processing costs and any share of revenue in a proposal after scoping. The pricing page shows the plans for standard accounts. For a platform proposal, talk to sales.
Who is responsible for compliance and card data on a platform?
Responsibility is shared, and the split is agreed during scoping. Card data is captured and tokenized in the environments of Lumino’s processor and gateway partners, which is why embedded checkout and hosted fields keep it off your servers. Your platform and its users still have obligations of their own, which depend on the integration. See compliance and PCI.
Is there developer documentation?
Integration details are shared during scoping. This site does not publish developer documentation.
Can users who already take payments elsewhere move to Lumino?
Yes, subject to underwriting, and the move is planned with you. Professional services looks at what those users have today, including stored cards and recurring schedules, and sets the order of migration in the implementation plan. Whether stored cards can be transferred depends on the outgoing processor’s policies.
How does reporting work across the merchants on a platform?
Through one portfolio view. Deposits, residuals, batches and chargebacks are shown across every merchant, and activity is grouped by MID so a single account can be followed on its own. The views are part of Reporting & Analytics. Dispute and VAMP ratios are covered under risk and compliance.
How is the platform program different from a standard Lumino account?
A standard account serves one business taking its own payments. The platform program is for a product whose users are the merchants: many businesses are onboarded, checkout is embedded in your interface, payouts to those businesses are handled through Lumino’s processing partners, and reporting covers the portfolio. A single business selling online should start with Online Payments.