Recipient identity
Identify the recipient and the relationship behind the transfer before funds ever move.
Operations / Payouts
Money coming in is only half the story.
Map how funds move from your platform to the people and businesses behind it. Keep recipient, timing, and operational review in view.
Illustrative distribution
Platform funds
Funds available for review
Partner
Recipient details
Vendor
Payout requirements
Design the outbound journey
Everything an outbound flow needs.
A payout is a decision about who gets paid, when, and why. Zapi keeps the recipient, the timing, and the operational review connected.
Timing control
Align the payout request with your platform's operating rules and cadence.
Operational review
Keep outbound activity visible so your team can follow each flow as it happens.
Requirements first
Payout destinations, timing, and availability depend on onboarding and applicable terms.
Destination context
Track where funds are going and what each destination expects from your platform.
Audit trail
Keep a clear record of outbound activity alongside the payments your business collects.
Every recipient adds a decision
Three questions for every payout.
Each outbound transfer asks your team to confirm who, when, and what happened. Keep the answers connected so nothing moves without context.
Who
Identify the recipient and the relationship behind the transfer.
When
Align the payout request with your platform's operating rules.
What happened
Keep outbound activity visible for your team to review.
Payout destinations, timing, and availability depend on onboarding and applicable terms.
The outbound journey
From platform funds to the right recipient.
A payout is a sequence of decisions, not a single action. Plan each step so the outcome is clear to your team.
01
Pool funds
Funds collected on your platform become available for outbound review.
02
Confirm recipient
Identify the partner, user, or vendor and the relationship behind the transfer.
03
Request payout
Align the request with your operating rules and the recipient's requirements.
04
Review outcome
Keep the outbound activity visible alongside your inbound payment flows.
Good to know
Payouts, explained.
What teams ask before they plan outbound money movement on Zapi.
Payouts go to the partners, users, or vendors your business has onboarded. Each recipient carries their own relationship and requirements, so destinations depend on your platform's setup and applicable terms.
You align each payout request with your platform's operating rules. Timing and availability depend on onboarding and the terms that apply to each recipient, so your team stays in control of when funds move.
Yes. Outbound flows stay visible alongside your inbound payment activity, so your operations team can follow each payout and confirm the outcome without searching across separate tools.
Yes. Inbound and outbound flows live in the same operational picture, so your team sees the full movement of money — what comes in and what goes out — in one place.
Related products
Explore more of Zapi.
Payments
The inbound payment layer that funds your payouts.
Customers
Keep recipient details and relationships on customer records.
Reporting
Bring outbound and inbound flows into one view.
Billing
Plan recurring relationships alongside outbound flows.
Invoicing
Collect the funds that later move outbound.
Checkout
Collect the first payment that starts a balance.
Start building with Zapi
Build what moves your business forward.
One integration for payments, payouts, and virtual accounts. Start in test mode and grow from there.