Platform and seller roles
Identify who sells the underlying goods or services, who contracts with the buyer, who handles complaints and refunds, and whether sellers require separate onboarding or visibility.
Payments for marketplaces
Payments for your marketplace. Connect buyers, sellers and orders.
ZyndPay supports approved marketplace payment journeys through hosted checkout, API, signed events, payout workflows and reconciliation. We review seller onboarding, account responsibilities and settlement requirements with your team before agreeing the integration scope.
- Marketplace payments
- Aggregator path separated
- Defined merchant responsibilities
Marketplace model
First decide whether the platform is a merchant, a marketplace or an aggregator.
These models create different customer, seller, custody, settlement and compliance duties. ZyndPay maps the actual contracting entity and funds flow before enabling live processing. Calling every multi-party platform an aggregator would hide the most important control decisions.
Funds-control boundary
Document where buyer money lands, whether it becomes a platform balance, how seller amounts are calculated and who authorizes any payout. Do not infer split settlement from a generic payments API.
Restricted-activity inheritance
A marketplace must know what its sellers offer. Platform approval does not make prohibited or unreviewed seller activity acceptable, and risk controls must account for portfolio behavior.
Aggregator qualification
A platform bringing a merchant portfolio follows the separate partner qualification path. Commercial territory users never gain control over ZyndPay transactions, balances, ledger or global operations.
Order and payout flow
Trace buyer payment, platform order and seller obligation separately.
A marketplace needs more than a “paid” flag. Stable references connect the buyer’s attempt to the platform order, while the platform retains its own seller obligation and only submits an eligible payout through an approved path.
- 01
Create the marketplace order
Record buyer, seller, goods or service, amount, currency and platform terms in the marketplace system. Send only the agreed payment data and a unique reference to ZyndPay.
- 02
Collect through an enabled path
Use hosted checkout or the supported API to present the stablecoin, card or mobile-money methods enabled for the account and transaction.
- 03
Confirm payment authoritatively
Consume signed events and authenticated status idempotently. The browser return can guide the buyer but does not prove that the platform can release goods or value.
- 04
Record the seller obligation
Apply fees, commissions, holds, refunds and seller entitlement in the platform’s approved accounting model. Do not treat the buyer charge as an automatic seller payout.
- 05
Submit and reconcile money out
Eligible payout instructions pass beneficiary, compliance, balance and approval controls. Match final payout evidence back to the seller obligation and original order.
Marketplace operations
Connect the lifecycle without inventing a sub-merchant product.
Buyer payment acceptance
Offer enabled payment methods through hosted or API-driven flows, each linked to the platform’s unique order reference.
Asynchronous order state
Use signed events, retries and replay-aware consumption so closed tabs and delayed rails do not corrupt the marketplace order.
Approved payout workflows
Submit money-out instructions to eligible beneficiaries through the account’s configured path, with screening and risk-based approval before execution.
Refund and dispute evidence
Keep buyer refund, payment reversal, seller obligation and marketplace dispute records linked but distinct.
Portfolio reconciliation
Reconcile orders, payment attempts, confirmed receipts, platform obligations, refunds and payouts using stable identifiers rather than aggregate balance changes.
Partner qualification path
Route true merchant-portfolio or territory proposals to the partner programme, where ownership, KYB readiness, technical responsibility and operating scope are assessed.
Responsibility boundary
A marketplace payment page is not a promise of split settlement or white label.
ZyndPay publishes only capabilities that are available through an approved account. Seller sub-accounts, automated splits, branded domains, delegated onboarding and platform liability require explicit product and contractual evidence; none is implied by this page.
- Buyer evidence
- The confirmed payment state proves the supported buyer collection. It does not itself prove delivery, seller entitlement or payout completion.
- Seller evidence
- The marketplace’s approved accounting model establishes what is owed to a seller. ZyndPay payout state establishes whether a submitted transfer completed.
- Commercial evidence
- Account pricing, limits, reserves and settlement are disclosed privately before live use. ZyndPay publishes no universal marketplace or partner commission.
Choose the right path
Choose a payment integration or explore a platform partnership.
Payments API
Connect marketplace order references to supported collection and status concepts from your back end.
Explore the payments APIPayout workflows
Understand beneficiary, approval, execution and reconciliation for eligible money-out instructions.
Explore payoutsAggregator partnership
Qualify a merchant-portfolio or territory operating proposal without publishing internal economics or control rights.
Explore partnershipsFAQ
Questions from marketplace teams
Does ZyndPay automatically split a buyer payment among sellers?
This page does not promise automated split settlement. The approved platform model determines how seller obligations are calculated and whether a supported payout path is available. Any sub-account or split feature must be verified explicitly before it is sold.
Can every seller use the marketplace after the platform passes KYB?
Not automatically. The marketplace and ZyndPay agree the seller, product and risk-review model. Platform approval does not legitimize prohibited goods, restricted services or unreviewed seller activity.
Can buyers pay with stablecoins and mobile money?
Enabled stablecoin, card and mobile-money methods may appear. The actual set depends on the account, market, currency, buyer context and current rail status.
When should the marketplace release an order?
Use the confirmed server-side payment state and the marketplace’s own fulfilment or escrow policy. A return page, screenshot or buyer message is not sufficient settlement evidence.
Is a marketplace the same as a ZyndPay aggregator partner?
No. A marketplace may simply accept payments for its own approved activity. An aggregator or territory proposal introduces a merchant portfolio and follows separate qualification, responsibility and contract steps through the partner programme.
Does ZyndPay publish marketplace or partner fees?
No universal rates or commissions are public. Applicable payment and partnership terms are account- and model-specific and are disclosed after qualification before live processing.
Platform qualification
Tell us how your marketplace works.
Share the legal entity, marketplace category, seller model, target countries, currencies, order lifecycle, refund rules, payout beneficiaries, compliance owner and technical owner. The team will separate the payment integration from any aggregator proposal.