Build for
|

|
|
|
|
Typical use cases |
Three patterns we've seen marketplace ISVs implement most often.
![]() Multi-vendor platformOnboard 1,000+ sellers, split payments between platform and seller, manage automated payouts. |
![]() On-demand servicesGig economy platform — contractor payouts after service completion, dispute management, fraud prevention. |
![]() B2B supplier marketplaceBusiness procurement platform with invoice-based purchasing, net-30 payment terms, and supplier settlement. |
Required stack |
What you'll wire up. Click any tile to see why it's in the recipe.
Accept PaymentsAuthorize and capture transactions across CP and CNP channels. required
APISDK
|
Unified CheckoutHosted UI for in-clinic and online payment. SAQ-A PCI scope. required
APISDK
|
Token Mgmt ServiceCard-on-file for wellness plan auto-renewal and repeat clients. required
APISDK
|
Merchant Onboarding (EC)White-label sub-merchant onboarding — KYC, bank verification, agreement sign. Embedded in your platform. recommended
Hosted No-code
|
Fraud Management EssentialsRule-based fraud screening per seller — different risk profiles per category. required
API
|
Decision ManagerML-based fraud scoring and velocity controls for high-volume marketplaces. required
API
|
||
Reporting & Transaction SearchPer-seller settlement reports, platform-level analytics, dispute management. required
API
|
WebhooksReal-time event streaming — payment captured, dispute opened, payout completed. required
API
|
Pay By LinkPayment links for off-platform transactions and invoice-based B2B purchasing. Hosted No-code
|
Digital InvoicingSupplier invoices with embedded payment for B2B procurement flows. API
|
Multi-Currency PricingCross-border marketplace — display in buyer's currency, settle in seller's currency. API
|
||
Recurring BillingSubscription marketplace fees — monthly platform charges to sellers. API
|
APIs |
Reference for every API in the stack, grouped by integration concern.
| API | REQUIRED | DESCRIPTION | DOCS |
| Payment Authorization | Authorize buyer transactions across CNP channels. | Docs ↗ | |
| Refund & Void | Buyer refunds, seller void flows, dispute reversals. | Docs ↗ |
Recommended ways for marketplace buyers to pay — minimize PCI scope while maintaining full UI control.
| API | REQUIRED | DESCRIPTION | DOCS |
| Unified Checkout | Hosted buyer-side checkout. Cards, wallets, 3DS. SAQ-A eligible. | Docs ↗ | |
| Flex Microform v2 | Custom checkout UI with server-side tokenization. | Docs ↗ |
| API | REQUIRED | DESCRIPTION | DOCS |
| Merchant Onboarding EC | White-label KYC and bank verification for sub-merchants. Embedded in ISV platform with zero Visa branding. | Docs ↗ | |
| Tokenization Service | Buyer card vault for repeat purchases across the platform. | Docs ↗ | |
| Fraud Management Essentials | Per-seller fraud screening with velocity controls. | Docs ↗ | |
| Reporting & Transaction Search | Per-seller transaction history, settlement, and dispute management. | Docs ↗ | |
| Webhooks | Real-time events: payment.authorized, payment.captured, dispute.opened. | Docs ↗ | |
| Decision Manager | ML-based fraud scoring — recommended for high-volume categories. | Docs ↗ | |
| Multi-Currency Pricing | Cross-border seller payouts in local currency. | Docs ↗ |
Vertical insights |
What's different about Marketplaces — surface the constraints before you architect.

![]() |
Integration path |
Five steps from sandbox to scaled platform.

Configure platform merchant profile, test sub-merchant onboarding flow, get test credentials.

Build: UC for buyer checkout, Merchant Onboarding EC for seller activation, webhooks for event handling.

Execute: buyer payment, sub-merchant activation, split payment, payout event via webhook, dispute flow.

Launch with pilot sellers, monitor fraud rates per category, validate settlement accuracy.

Onboard seller cohorts — KYC automation via EC, per-category fraud tuning, multi-currency expansion.
![]() |
Other recipes you might combine |
Many veterinary platforms also build for these adjacent verticals.
|
|
|
Developer MCPUse natural language to generate integration code, explore APIs, and debug your implementation. The Visa Acceptance Developer MCP connects your AI coding assistant directly to our documentation and sandbox. |