Skip to main content
Commerce V2 supports four distinct operating models to match your business needs. Each model offers different capabilities and is designed for specific use cases, from single merchant setups to complex multi-party payment ecosystems.
The default model for single businesses. Your account operates as a standalone merchant processing its own transactions.

​
Key Features

  • Single merchant configuration locked to your primary account
  • Simplified setup - No sub-merchant management required
  • Full payment features - Access to all payment capabilities for your own transactions
  • Restricted operations:
    • Cannot add sub-merchants (POST /merchants disabled)
    • Cannot delete the primary merchant (DELETE /merchants/{id} disabled)

​
Use Cases

  • E-commerce stores
  • SaaS businesses processing their own payments
  • Single-entity businesses
  • Startups and small businesses
This model is ideal when you’re processing payments for your own business without the need to facilitate payments for other parties.

​
Choosing the Right Model

Selecting the appropriate operating model depends on your business structure and requirements:
  • Primary Merchant: Choose this if you’re a single business processing your own payments
  • Platform / Marketplace: Ideal for platforms connecting multiple sellers or service providers
  • Ecosystem: Best for networks of partners or franchise operations
  • Managed Ecosystem: Suitable for large-scale payment facilitation with full-service management

​
Migration Between Models

Your operating model is typically set during account creation. If your business needs change, contact your account manager to discuss migration options. Some transitions may require account reconfiguration or compliance review.

​
API Capabilities by Model

All operating models support the core Commerce V2 features:
  • Payment processing (customer and merchant initiated)
  • Token management
  • 3D Secure authentications
  • Network token provisioning
  • Payment modifications (capture, void, refund)
The differences lie in merchant management capabilities, sub-merchant support, and transaction splitting features. Refer to the Merchants API documentation for model-specific endpoint availability.