Marketplaces

Embed collection, payment accounts, commissions, payouts and seller verification directly in your marketplace journey.

Organise flows between buyers, sellers, providers or partners inside financial infrastructure connected to your product.

Explore our API
  1. Buyer
  2. Payment
  3. Split
  4. Commission and payouts

A chain of flows, not a standalone checkout

In brief

A marketplace does not handle a payment. It orchestrates a chain of flows.

When a buyer pays for an order on a marketplace, the payment does not stop at checkout. The transaction must be identified, funds tied to the right order, beneficiaries determined, the platform commission calculated, payouts organised, any refunds handled, and the matching statuses returned.

CollectSplitPay outReconcileSteerA marketplace orchestrates a chain of flows.

Marketplace flows

One collection. Several destinations.

A marketplace inherently organises flows between several parties. Tractial can assess an architecture that fits the platform’s economic model, its users and the agreed split rules.

Buyer

  1. Buyer €100

Payment tied to the transaction.

Tractial

Embedded financial infrastructure

  • Accounts
  • Payments
  • Commissions
  • Payouts
  • KYC / KYB

Payment.net

Destinations

  1. Marketplace
  2. Seller A
  3. Seller B
Teaching diagram. Account structure, how funds are characterised, split mechanics and respective duties are defined during scoping and contracting.

  1. Buyer

    Payment initiated from the marketplace.

  2. Payment

    Processed in the defined infrastructure.

  3. Transaction

    Tied to the business object.

  4. Split

    Amounts determined according to the model.

  5. Commission

    Remuneration tracked according to the model.

  6. Payout

    Funds paid out according to the applicable conditions.

Embedded experience

Make payment a native marketplace function

Payment can become part of the product rather than a separate journey. The aim is to connect financial actions to objects already in the platform: user, seller, basket, order, service, file or subscription.

Tie the payment to the order

Connect the buyer’s settlement to the relevant transaction so the order and the financial flow stay continuous.

Teaching example. Fictional data.

Order
#45832
Amount
€248.00
Payment
Received
Reference
PAY-45832

Multi-seller payment

Multi-seller payment becomes a workflow

On a marketplace, a single basket can correspond to several economic relationships. The difficulty is not only accepting a payment, but keeping a reliable view of what belongs to each party.

  1. Multi-seller basket
  2. Buyer payment
  3. Transaction identification
  4. Split rules
  5. Payouts
  6. Statuses and reporting

KYC / KYB

Onboard sellers in the same journey

Before a seller, provider or partner joins a payment arrangement, checks may be required. Tractial can embed the KYC or KYB journeys that fall within the project perimeter into the marketplace experience.

  1. Profile creation
  2. Information
  3. Documents
  4. Checks
  5. Review
  6. Activation
  7. Ongoing monitoring

Money in / Money out

Two sides of the same flow: collect and pay out

Money in

Collection

  1. Order created
  2. Payment initiated
  3. Payment received
  4. Transaction identified
  5. Amount matched
  6. Split calculated

Tractial

Embedded financial infrastructure

  • Payment accounts
  • Incoming payments
  • Transfers
  • Commissions
  • Payouts
  • Statuses
  • Reporting
  • KYC / KYB

Money out

Payout

  1. Beneficiary identified
  2. Conditions checked
  3. Amount allocated
  4. Payout prepared
  5. Operation executed
  6. Status returned

Building blocks

Build the journey that fits your marketplace

  • Payment account

    Tie flows to a user, a company or a journey when the model requires it.

  • IBAN

    Receive or identify incoming transfers when the use case requires it.

  • Card payment

    Embed card payment when that method matches the chosen journey.

  • Incoming transfers

    Identify received settlements and tie them to the matching business objects.

  • Commissions

    Calculate and return information about the marketplace’s remuneration.

  • Payouts

    Organise payments to sellers, providers or beneficiaries.

  • Multi-party flows

    Structure transactions involving several beneficiaries when the model allows it.

  • Refunds

    Embed refund handling and tracking.

  • KYC / KYB

    Connect the verification steps the user journey needs.

  • Statuses

    Return the events that operational tracking needs.

  • Reporting

    Give teams the data they need to steer operations.

  • API and webhooks

    Synchronise financial events with marketplace interfaces.

Models

B2B, B2C, C2C: each marketplace has its own flow architecture

  • B2B

    Businesses to businesses

    Professional transactions, KYB, transfers and reconciliation.

  • B2C

    Consumers to professional sellers

    Buyer payment, seller onboarding, commissions and refunds.

  • Services

    Client to provider

    Payment tied to a service, assignment, booking or milestone.

  • C2C

    Individuals to individuals

    Specific identification, payment and control journeys to assess.

API and embedded finance

Financial infrastructure designed to stay inside your product

The aim is not to add a new tool that the buyer or seller must learn. Financial services can be connected to the marketplace’s existing interfaces and workflows.

Your marketplace

  • Catalogue / services
  • Basket
  • Orders
  • Buyer interface
  • Seller interface
  • Back office
  • Commissions
  • Support

API and webhooks

Tractial / Payment.net

  • Accounts
  • IBAN
  • Incoming payments
  • Transfers
  • Payouts
  • Statuses
  • Reporting
  • KYC / KYB

Integration

  1. Map the flows
  2. Define responsibilities
  3. Validate the model
  4. Connect the APIs
  5. Test the workflows
  6. Activate progressively

API and integrations

Operational tracking

Follow a transaction from order to payout

A marketplace must be able to answer a simple question: where is the money?

Teaching statuses.

OrderAmountPaymentSplitPayout
#45832 · Client #1892€248.00ReceivedValidatedExecuted / scheduled
#45833 · Client #1893€89.00ReceivedValidatedScheduled

Integration depth

API, white label or a more involved model: choose the right level of intervention

  • API integration

    The marketplace keeps its interfaces and connects the financial functions its product needs.

    See the page

  • White-label journey

    A deeper integration can be assessed so the experience stays consistent with the platform’s brand and journey.

    See the page

  • Payment institution agent

    For models that require the platform to take a larger role in providing payment services, payment-institution agent status can be assessed.

    See the page

Regulatory framework

Two complementary roles

The marketplace

  • Organises its offer or catalogue
  • Lists sellers and providers
  • Manages orders or services
  • Defines its economic model
  • Sets its commission
  • Designs the user experience
  • Handles its own commercial duties

Tractial

  • Provides the chosen payment infrastructure
  • Operates the payment services within its perimeter
  • Embeds the planned KYC / KYB controls
  • Executes or processes operations that match the validated model
  • Returns available statuses and data
  • Provides the traceability that falls within its perimeter

Integrating Tractial does not confer payment-institution status on the marketplace.

FAQ

What is a marketplace payment solution?

A marketplace payment solution organises financial flows between several parties: buyer, platform, seller, provider or partner. It can cover collection, commissions, payouts, refunds, user verification and reporting, depending on the chosen perimeter.

Can a marketplace collect money intended for its sellers directly?

Collecting funds intended for third parties is a regulated activity. The model must therefore be analysed to determine the exact role of the marketplace, that of the payment-service provider, and the appropriate architecture.

How does payment work on a multi-seller marketplace?

A payment can be tied to an order that includes several sellers. Transaction data identifies the different beneficiaries and the amounts allocated to them according to the agreed rules.

Can a marketplace take its commission automatically?

A commission logic can be embedded in the financial journey when the technical, contractual and regulatory model allows it.

When does the seller receive their money?

The payout calendar depends on the marketplace model, the payment methods used, operational rules, required controls and the applicable contract.

How are sellers verified?

Professional sellers may in particular follow a KYB journey. For individuals, a KYC journey may be required.

Can foreign sellers be verified?

International journeys can be assessed. Coverage depends on the countries involved, user categories, services offered and applicable verification options.

Can Tractial handle baskets with several sellers?

Multi-party flows are among the use cases that can be assessed. The model must specify basket structure, beneficiaries, commission rules and the events that trigger payouts.

How are refunds handled?

A refund must stay tied to the original transaction and take into account the payment’s status, any split already made, and the beneficiaries involved.

Can payments be embedded in the marketplace interface?

Tractial’s infrastructure is designed to be connected to partner products through the interfaces available for the project.

What is the difference between a payment account and a bank account?

A payment account is used to execute payment operations within the perimeter of the provider that holds it. It must not be presented as a classic bank account when the functions and legal framework differ.

Must a marketplace become a payment institution?

Not necessarily. Depending on the model, a marketplace can embed financial services by relying on a licensed institution. For some projects, payment-institution agent status can also be assessed.

How do you start a project with Tractial?

The first step is to map the flows: who pays, who receives, why, when, in which countries, which commission is taken and who must be verified.

Go further on the building blocks of your project

Accounts and IBANs

The payment-account building block.

See the page

Incoming and outgoing payments

Collection, payouts and statuses.

See the page

KYC / KYB

Seller verification.

See the page

API and integrations

Connect the flows to the product.

See the page

White label and grey label

Presentation and responsibilities.

See the page

Marketplace and payments

Building or evolving a marketplace?

Connect payments, accounts, commissions, payouts, KYC/KYB and reporting directly to your journey. Show us your model, your users, your flows and the financial functions you want to embed.

Explore our API

Payment institution licensed by the ACPR, CIB 16748. Services are offered subject to eligibility, compliance validation, contracting, technical availability and the applicable regulatory framework.