Marketplace

Run the money side of a multi-seller platform: onboard merchants through KYB, split each settled order between platform fee and merchant share, and pay sellers out through the reconciliation disbursement workflow. Built on the Straventa Payment Gateway, FDS, and Reconciliation Engine. This is the money layer only — it does not ship a storefront, a catalogue, or per-merchant subdomains.

Every merchant gets a branded storefront at Per-merchant settlement entity.

Start Free Trial Book a Demo

Per-merchant settlement splits reconciled against the bank file

Per-Merchant Subdomain

Every merchant gets .straventa.com

On day one, every merchant on your marketplace is reachable at Per-merchant settlement entity — branded storefront, isolated catalogue, TLS auto-provisioned, all managed from one platform.

acme.straventa.com
kopi-bali.straventa.com
warung-pak-budi.straventa.com

https://acme.straventa.com

Acme

Acme Coffee Co. — Specialty roasts, shipped fresh.

Shop now →

How It Works

From signup to live storefront in minutes

Merchant onboards

Merchant signs up and completes KYB through Straventa KYC before any money can move to them.

Merchant starts transacting

The merchant is attached to the gateway and every order it settles is split and booked against its own ledger position.

Buyer Pays via PG

Buyers check out through the Straventa Payment Gateway — split payment routes the platform fee and merchant share automatically.

Risk + Reconciliation

Every order is scored by FDS and logged to the Reconciliation Engine. Disputes, refunds, and payouts settle in one ledger.

Marketplace Architecture Diagram

Key Features

Everything you need to launch a multi-merchant marketplace.

Per-merchant settlement

Each merchant is its own settlement entity with its own MDR, payout schedule, and reconciled ledger position.

Merchant Onboarding KYB

Built-in KYB flow checks NPWP, NIB, and bank account — orchestrated through Straventa KYC.

Merchant onboarding

Sellers onboard through Straventa KYB before they can be paid, with the verification record attached to the merchant.

Split Payments & Payouts

Settled funds split per-order between platform fee and merchant. Bulk payouts via the Reconciliation Engine's disbursement workflow.

Marketplace-Wide Fraud Controls

Cross-merchant fraud signals — repeated chargeback buyers, suspicious refund patterns — surface through Straventa FDS.

Payouts on the same ledger

Seller payouts run through the reconciliation disbursement workflow with maker-checker approval, so every payout is already reconciled when it leaves.

Regulatory Control Mapping

Built for Indonesian regulations

OJK — Penyelenggara Jasa Pembayaran (PJP) license requirements for marketplace acquirers

BI — QRIS settlement rules for multi-merchant aggregators

PPATK — KYB and ongoing monitoring obligations across merchants

Plugged into the rest of Straventa

Marketplace orders flow through our Payment Gateway, are scored by FDS, monitored by AML, and reconciled automatically. See the end-to-end flow.

See Full Platform Flow Enterprise Inquiry

How it compares

Straventa Marketplace vs building on a gateway's platform APIs

Xendit, Midtrans, and DOKU give a platform business the payment primitives — sub-accounts, splits, disbursement APIs — and leave the storefront, catalogue, merchant onboarding, and payout controls to you. Straventa Marketplace ships those parts: a branded storefront per merchant at its own subdomain, KYB onboarding orchestrated through Straventa KYC, split payouts running through a maker-checker disbursement workflow, and cross-merchant fraud signals. The trade is real and worth stating plainly: those vendors are licensed and Straventa is not, so the acquiring licence and settlement account behind your splits still belong to your bank or PJP partner.

Straventa Marketplace vs building on a gateway's platform APIs
Criterion	Straventa Marketplace	Xendit (XenPlatform)	Midtrans	DOKU
What you actually get	The money layer for a multi-seller platform: KYB onboarding, per-merchant settlement splits computed against the bank file, and seller payouts through the maker-checker disbursement workflow — on the same ledger as the rest of your payments. This is the money layer only — storefront, catalogue, and per-merchant subdomain provisioning are not part of the product.	A sub-account and split-payment layer for platforms. You still build the storefront, the catalogue, and the merchant experience.	Acceptance plus disbursement APIs you compose into splits. Storefront and merchant management are yours to build.	Acceptance plus disbursement APIs for platforms. Storefront and merchant management are yours to build.
Merchant onboarding / KYB	Built in — NPWP and NIB document extraction orchestrated through Straventa KYC, which also runs KTP capture and liveness for individuals. Live registry verification and bank-account checks are not enabled yet.	Sub-account onboarding and KYC run by the provider under its own licence — less work for you, and less control over the criteria and the timeline.	Merchant approval runs through the provider's own onboarding process, on its criteria.	Merchant approval runs through the provider's own onboarding process, on its criteria.
Payouts to merchants	Settled funds split per order between platform fee and merchant share, with bulk payouts through the Reconciliation Engine's disbursement workflow and bank-native exports (BCA CSV, Mandiri MCC, BNI Direct Debit, generic CSV).	Disbursement API to Indonesian banks and e-wallets, priced per transfer.	Disbursement API to Indonesian banks, priced per transfer.	Disbursement API to banks and wallets, priced per transfer.
Controls on money leaving	Maker-checker with multi-level approval: batches above a per-tenant threshold escalate to CFO sign-off, the maker can never be the approver, and every action lands in an immutable audit log held to statutory retention floors.	Dashboard user roles and API keys. A two-person approval rule on a payout batch is something you design and enforce yourself.	Dashboard user roles and API keys. Approval workflow is your build.	Dashboard user roles and API keys. Approval workflow is your build.
Cross-merchant risk	Marketplace-wide fraud signals — repeat chargeback buyers, suspicious refund patterns — surface through Straventa FDS on the same record, with AML typology monitoring behind it.	Per-transaction fraud screening at the gateway; correlating abuse across your merchants is your data problem.	Per-transaction fraud screening at the gateway; cross-merchant correlation is your data problem.	Per-transaction fraud screening at the gateway; cross-merchant correlation is your data problem.
Deployment and residency	SaaS or on-premise — the marketplace module deploys with the rest of the platform inside your own infrastructure in Indonesia. On-prem quoted per deployment.	SaaS only; platform and merchant data live in the vendor's environment.	SaaS only; platform and merchant data live in the vendor's environment.	SaaS only; platform and merchant data live in the vendor's environment.
Pricing model	Rp 1.500 per split or 0,15% of GMV — directional, billing not yet active. On-premise licensed per deployment.	Per-transaction acceptance rates plus a per-disbursement fee; platform features come with the account.	Per-transaction acceptance rates plus a per-disbursement fee.	Per-transaction acceptance plus per-disbursement fees, quoted per merchant.
Honest limits	Straventa is not the licensed party — the acquiring licence and settlement account behind these splits belong to your bank or PJP partner — and the Ledger / Wallet escrow module is roadmap, not shipped. If you need a regulated sub-account structure live this quarter, the licensed platforms are the shorter path.	You cannot run it in your own environment, and the sub-account model is the vendor's to change, not yours.	SaaS only, and splits are something you compose rather than a marketplace product you buy.	SaaS only, and splits are something you compose rather than a marketplace product you buy.

Competitor rows describe each vendor’s publicly documented model at time of writing; confirm current terms with the vendor before making a decision.

How it is priced

You pay per split rather than per merchant seat — and on-premise you stop paying by volume at all.

Billing model

Per split or % of GMV; per-deployment licence on-premise

Rp 1.500 per split, or 0,15% of GMV. Directional only; billing is not yet active and no payment is collected today.
The rate is identical on the starter and growth tiers — the model does not change as you scale, only the volume does.
On-premise is quoted per deployment ("Contact us"). Merchant count and GMV do not move the licence fee.
Included in the Platform Bundle at Rp 22.000.000/mo, which is the sane path if you also need gateway, KYC, fraud, AML, and reconciliation underneath the marketplace.

See the full price list

Map Straventa to your operating model.

Bring your rails, controls, and deployment constraints. We will show where the platform fits and where it does not.

Book a demo Explore the platform