Loading, please wait…
Payouts supports multiple payout models that allow platforms to determine how recipient funds are held, managed, and delivered.
The right payout model depends on factors such as recipient expectations, business objectives, user experience requirements, operational controls, and the financial capabilities the platform wants to provide.
At a high level, Payouts supports two primary models:
Understanding the differences between these models can help you design the payout experience that best aligns with your business goals.
The Embedded Fiserv-Enabled Payout model allows platforms to direct funds into Fiserv-managed financial accounts that exist within the platform ecosystem.
Instead of immediately sending funds externally, recipients can maintain balances within supported account structures and access funds through platform-enabled financial experiences.
This model is designed for platforms that want to provide enhanced financial capabilities while maintaining greater visibility and control over recipient balances.
Common Scenarios
Business Benefits
Refer to the Embedded Fiserv-Enabled Payouts section to learn more.
The Non-Embedded Payout model delivers funds directly to financial destinations owned or controlled by the recipient.
Funds are transferred outside the platform ecosystem using supported payout methods such as bank accounts, debit cards, digital wallets, and other approved payout destinations.
This model is designed for platforms that want to provide traditional payout experiences where recipients receive funds through financial accounts they already use.
Common Scenarios
Business Benefits
Refer to the Non-Embedded Payouts section to learn more.
Payout models are not mutually exclusive. Many platforms support multiple payout experiences across different participant types, regions, products, or business scenarios.
For example, a platform may allow some recipients to maintain balances in Fiserv-managed accounts while allowing others to receive funds directly through external bank accounts, debit cards, or digital wallets.
This gives platforms flexibility to tailor payout experiences to recipient preferences and business requirements.
| Capability | Embedded Fiserv-Enabled Payouts | Non-Embedded Payouts |
|---|---|---|
| Destination of Funds | Fiserv-managed account within the platform ecosystem | External financial destination |
| Balance Retention | Supported | Not supported |
| Internal Fund Movement | Supported | Not applicable |
| Recipient receives fund in an existing external account | Optional | Yes |
| Embedded Financial Experiences | Supported | Not applicable |
| Primary Destination | Platform-managed account | External account |
| Typical Recipients | Sellers, workers, merchants, and providers maintaining balances within the platform | Sellers, workers, merchants, and providers receiving funds externally |
Consider the following questions when selecting a payout model:
| Scenario | Payout Model |
|---|---|
| Retain balances within the platform ecosystem | Embedded Fiserv-Enabled Payouts |
| Offer wallets or account-based experiences | Embedded Fiserv-Enabled Payouts |
| Support embedded financial services | Embedded Fiserv-Enabled Payouts |
| Deliver funds to existing bank accounts | Non-Embedded Payouts |
| Support traditional marketplace payouts | Non-Embedded Payouts |
| Enable global recipient disbursement | Non-Embedded Payouts |
| Provide recipients with payout destination flexibility | Non-Embedded Payouts |
After selecting a payout model, explore the detailed implementation and operational considerations: