Organize the recipients and preserve the financial context associated with each operation.
Infrastructure for marketplaces
Many participants.
Many participants.
One coordinated financial operation.
Connect sellers, payments, splits, transfers, reconciliation and integrations into an architecture ready to grow with your product — without fragmenting the financial transaction.
Financial architectureMarketplace in operation
Operational coordinationOne layer for payments, sellers, rules and settlement.
The resultMore context to grow without creating parallel controls.
Origin of the speciesOrder / saleThe operation is born in the trade flow, without loss of context.
ParticipantsSellersCount, ID and rules per receiver.
DistributionSplit & passesThe financial rules remain tied to the sale.
ClosureReconciliationRequest, seller and traceable settlement on the same track.
Relate payment and financial division without relying on parallel calculations.
Sales, distribution and settlement remain connected on the same track.
It integrates financial flow into product, ERP, back office and internal systems.
Infrastructure
A financial layer prepared for multiple participants.
The marketplace doesn't need to spread its operations across isolated systems. IOPAY connects the main financial elements for product and backoffice to work on the same structure.
Context by participant.
Keep seller, recipient and trade reference identifiers throughout the payment flow.
Integrated means.
Connect the enabled means of payment to your product experience and to the context of the request.
Distribution from the source.
When the model requires multiple receivers, the split rule can accompany the sale rather than being born on a later spreadsheet.
Sales and finance are on the same trail.
It reduces ambiguities between what was sold, processed, distributed and effectively liquidated.
Webhooks for automation.
Receive notifications of status changes and integrate operation updates to your backend.
Tailored integration.
Use API REST and the transaction credentials to connect the financial infrastructure to the marketplace architecture.
45 examples of operations
Where a marketplace architecture can make sense.
There's no one type of marketplace. The common pattern is the existence of multiple economic participants, sellers or providers connected by a single platform. Below are 45 models that often benefit from participant management, split, financial reconciliation and automation — including startups, fintechs and apps that pay creators, affiliates, partners and agents.
45 models
Third-party stores selling within the same digital experience.
Sellers · split · reconciliationManufacturers, distributors and corporate buyers connected by a single platform.
Orders · suppliers · transfersCentral orders with restaurants and establishments as participants in the sale.
Establishments · settlementA single shopping trip involving different brands or kitchens.
Multiple marks · splitPlatforms connecting passengers, drivers or fleet operators.
Providers · events · transfersOperations with independent carriers, suppliers or logistics partners.
Partners · conciliationReservations connecting guests, hosts, hostels or operators.
Reservations · receiversLocal operators offering tours, activities and experiences on a single platform.
Operators · splitTickets sold involving producers, houses, organisers and partners.
Events · participantsTeaching platforms with different teachers, schools or content producers.
Teachers · recurrenceScheduling and collection involving clinics, specialists and independent providers.
Professionals · ConciliationSalons, studios, therapists and professionals offering services on the same platform.
Agenda · providersElectrician platforms, technicians, cleaning, renovation and local services
Providers · paymentsPet sitters, hotels, bath and toilet, trainers and clinics in a digital ecosystem.
Services · receiversPlatforms that market content, sessions, mentoring or products from multiple creators.
Creators · distributionDigital apps, extensions, integrations or services offered by different developers.
Developers · digital salesOperations that need to organise financial flows between independent entities, brands or operators.
Unit · reconciliationPlatforms connecting producers, distributors, buyers and suppliers of the agricultural ecosystem.
B2B · participantsMarketplaces for consultancy, design, technology, legal and other professional services.
Providers · transfersOffices, parts suppliers, services and operators gathered on the same trip.
Suppliers · paymentsPlatforms that pay creators for content, subscriptions, tips, sales or performance.
Creators · monetization · transfersOperations that calculate and distribute commissions for sales, leads or allocated conversions.
Members · commission · trackingBrands hiring multiple creators for campaign and delivery-related remuneration.
Creators · campaigns · payoutSales in broadcasts involving hosts, creators, sellers and business partners.
Lives · creators · splitApps that reward customers, members or ambassadors for new users, sales or activations.
Indication · commission · partnersEcosystems that share revenue with publishers, affiliates, communities or acquisition partners.
Cashback · publishers · revshareNetworks that monetize subscriptions, advertising or sponsorship and pay different producers.
Content · subscriptions · creatorsLicensing marketplaces with photographers, video makers, musicians and other content holders.
Licensing · royalties · creatorsOperations that need to organize values between artists, labels, producers and other economic participants.
Royalties · participants · conciliationGame platforms, communities or tournaments that pay streamers, teams and partners.
Gaming creators awardsMarketplaces where developers receive digital components for sale or subscription.
Developers · subscriptions · revshareProviders of APIs, data sets or specialized services marketed for use or subscription.
APIs · suppliers · consumptionPlatforms that remunerate independent agents or representatives for sales and originating contracts.
Agents · commission · salesPortals and platforms connecting real estate, owners, brokers and trading partners.
The Commission shall be responsible for the implementation of the measures.Marketplaces for equipment, vehicles, spaces or other assets made available by third parties.
Rental and transfer servicesCreators sell products under their brand while production, fulfillment and remuneration are distributed among partners.
Creators · production · splitCommunities that curate products or services and share revenue with administrators, creators or partners.
Community · curation · revshareSoftware companies with partners that indicate, resell or deploy solutions in exchange for commission.
SaaS · partners · commissionProjects sold by one company and executed by different agencies, consultants or partner experts.
Projects · partners · distributionApps that pay people for tasks, visits, collections, audits, surveys or services performed.
Tasks · agents · payoutsFintechs that connect customers to different products, partners or suppliers and need to organize commissions, participants and conciliation.
Fintech · partners · revenue shareSoftware startups that incorporate payments and remunerate partners, units, professionals or customers within the product itself.
Start-up · SaaS · embedded financePlatforms that connect brokers, partners, insurers and providers with different trade events and commissioning.
The Commission will also be consulted on the following issues:Platforms connecting customers, correspondents, originators and partner institutions, in accordance with the applicable regulatory framework.
Fintech · credit · originationStartups and scale-ups that monetize a network of suppliers, experts, affiliates, distributors or partners within the product itself.
Start-ups · scale-ups · partnersNo model found.
Try another term or remove the filters.
These 45 examples describe business models that can adopt marketplace or multi-receiver architecture. The regulatory, fiscal and contractual framework depends on the role the platform effectively plays in the financial flow and should be analysed on a transaction-by- transaction basis.
Scale with governance
The more sellers, the less room for parallel controls.
In operations with many participants, the challenge is more than just accepting payment. The marketplace needs to know who participated in the sale, what rule was applied, what each party has to receive and how the value got to the final destination.
Orderedpreserved trade reference
Selleridentified participant
Splitthe financial rule
settlementTraceable financial event
Reconciliationconsolidated view of the operation
API & webhooks
Connect the marketplace to your own architecture.
IOPAY's public documentation provides integration by REST API, credentials with IO_Seller_ID and webhooks for event updates. This allows the payment infrastructure to be linked to the demand, seller and internal marketplace systems.
IOPAY integrationREST · seller ID · webhooks
CredentialsIO_Seller_IDIdentifier used in the merchant account integration credentials.
Referencereference_idAssociate the transaction with the identifier used by your own application or system.
EventsWebhooksReceive notifications of changes in status and see transaction details by the informed ID.
Payment Split
Marketplaces and split work better together.
The marketplace organises the participants and the context of the operation. The split organises the financial distribution of the sale. When the two are born connected, the closure becomes simpler and traceable.
Frequent Questions
It's a financial marketplace, no black box.
The main points for structuring payments with multiple participants.
What does IOPAY call a seller?
Seller is the participant or seller account identified within the transaction. The public documentation of IOPAY uses IO_Seller_ID as one of the integration credentials.
Marketplace and split are the same thing?
- No, I'm not. The marketplace organizes participants, product and operation; the split represents the financial distribution between the recipients when that model becomes part of the sale.
Can I integrate into my ERP or back-end?
- I know. IOPAY provides API REST for custom integration and webhooks for transaction event updating.
How does reconciliation help the marketplace?
It relates order, transaction, seller, distribution, receivables and settlement to explain how much was sold, how much each participant was paid and what was actually received.
Every marketplace is automatically a sub-accreditor?
- No, I'm not. The framework depends on the role effectively played by the platform in the flow of payments and the legal and financial structure adopted. The model shall be analysed on a case by case basis.
Is it just for e-commerce?
- No, I'm not. Marketplaces can connect products, services, professionals, logistics operators, restaurants, creators, B2B suppliers and many other types of participants.
IOPAY
Build the financial layer of your marketplace.
Connect participants, payments, splits, reconciliation and integrations into an architecture ready to grow with your operation.