Embedded Fiserv-Enabled Payouts
Embedded Fiserv-Enabled Payouts allow platforms to deliver funds into Fiserv-managed financial accounts rather than immediately sending funds to an external bank account, card, or digital wallet.
Recipients receive funds into a platform-enabled account experience, where balances can be maintained, viewed, transferred, spent, or withdrawn based on the capabilities enabled by the platform.
This approach is commonly used when a platform wants to provide embedded financial experiences, support balance retention, or maintain greater visibility into recipient funds.
How Embedded Payouts Work
With an embedded payout model, funds are delivered to a Fiserv-managed account or wallet rather than being immediately distributed to an external destination.
The recipient receives an account-based experience where funds can be retained within the platform ecosystem and accessed through capabilities enabled by the platform.
For information about how payout instructions are created and processed, see Payout Instructions.
Recipient Experience
Recipients access funds through a platform-enabled financial account experience.
Depending on the capabilities offered by the platform, recipients may be able to:
- View available balances
- View transaction history
- Maintain funds within an account or wallet
- Transfer funds internally
- Spend available balances
- Withdraw funds to external destinations
The specific actions available to recipients depend on the services enabled by the platform.
Benefits of Embedded Payouts
Support Balance Retention
Recipients can maintain funds within the platform ecosystem rather than immediately transferring them externally.
Increase Visibility
Platforms maintain visibility into balances, activity, and fund movements within platform-managed accounts.
Enable Account-Based Experiences
Embedded payouts support financial experiences that extend beyond traditional fund disbursement.
Support Internal Money Movement
Funds can move within platform-managed accounts before being withdrawn externally.
Supported Embedded Destinations
Embedded payouts may be directed to one of several FFP-managed destinations depending on the solution being implemented.
Examples include:
- Wallets
- Seller earnings accounts
- Demand Deposit Accounts (DDAs)
- Issued accounts
- Other supported embedded financial account structures
The available destination types depend on the capabilities enabled for your platform.
Accessing Funds
Unlike traditional payouts that immediately send funds to an external account, embedded payouts allow recipients to maintain balances within the platform ecosystem.
Depending on the enabled capabilities, recipients may:
- Retain funds within an account or wallet
- Transfer funds internally
- Spend available balances
- Withdraw funds to external destinations
This flexibility allows platforms to design account-based financial experiences that align with their business model and recipient needs.
Considerations
When evaluating an embedded payout model, consider:
- Whether recipients should maintain balances within the platform ecosystem
- How recipients will access and manage funds
- Whether account-based experiences align with your business model
- How and when funds may leave the ecosystem
- Regulatory and compliance requirements associated with account-based financial experiences
Dependencies
Embedded payouts require a valid Fiserv-managed destination capable of receiving funds.
Examples may include:
- Wallets
- Earnings accounts
- Platform-managed financial accounts
- Other supported embedded account structures
The destination account must be established and able to receive funds before an embedded payout can be completed.