Integration Approaches
Commerce Hub for Platforms offers multiple integration approaches that allow you to balance implementation effort, customization, participant experience, and operational ownership. Depending on your business requirements, you can leverage Fiserv-managed experiences, embed platform capabilities directly into your application, or build fully customized workflows using APIs.
Integration approaches can be used independently or combined across different capabilities.
Available Integration Approaches
Commerce Hub for Platforms supports three integration approaches:
Hosted Experience
Provides ready-to-use workflows that are managed and maintained by Fiserv.
With Hosted Experiences, Commerce Hub for Platforms provides and maintains the user experience while your platform focuses on directing participants into the appropriate workflows.
Best for
- Accelerating time to market
- Reducing implementation complexity
- Leveraging out-of-the-box onboarding experiences
- Lower maintenance responsibilities
Typical Use Cases
- Seller onboarding
- Account management
- Operational workflows
Customer Experience

The participant is redirected to a Fiserv-managed experience to complete the workflow.
Embedded Experience
Embedded experiences allow participants to interact with Commerce Hub for Platforms capabilities while remaining within your application.
This approach combines a seamless participant experience with Fiserv-managed functionality.
Embedded Experiences allow Fiserv-managed workflows to appear within your platform, reducing implementation effort while preserving your platform branding and user journey.
Best for
- Consistent participant experiences
- Balanced customization and implementation effort
- Branded platform experiences
Typical Use Cases
- Onboarding flows
- Account experiences
- Wallet experiences
- Operational dashboards
Customer Experience

Participants remain within your application while interacting with Commerce Hub for Platforms powered experiences.
API-led Experience
API Integrations provide direct access to Commerce Hub for Platform services, enabling platform owners to build their own workflows and user experiences.
This approach offers the greatest level of flexibility and allows platform operators to control the end-to-end user experience.
Best for
- Custom participant experiences
- Unique business requirements
- Advanced operational requirements
- Complete workflow ownership
Typical Use Cases
- Custom onboarding experiences
- Payment workflows
- Payout orchestration
- Platform-specific journeys
Customer Experience

Your application manages the user experience and interacts directly with Commerce Hub for Platforms services through APIs.
Comparing Approaches
| Requirement | Hosted | Embedded | API-led |
|---|---|---|---|
| Fast implementation | ✅ | ✅ | |
| Reduced development effort | ✅ | ✅ | |
| Consistent platform branding | ✅ | ✅ | |
| Custom workflows | Limited | ✅ | |
| Complete experience ownership | ✅ | ||
| Lower maintenance | ✅ | ✅ |
Key Considerations
When selecting an integration approach, consider:
- Desired user experience
- Internal development resources
- Time-to-market goals
- Ongoing maintenance responsibilities
- Required customization
- Long-term platform roadmap
There is no single recommended approach for all platforms. Most organizations choose the combination of approaches that best supports their participant experience and operational requirements.
Related Topics
Once you understand the available integration approaches, determine how participant onboarding should be implemented for your platform.