Co-Seller Payout Transfer Troubleshooting
How to interpret pending and failed co-seller transfer states, when Retry transfer is appropriate, and what creators should fix before retrying.
Where you see this in the app
This page documents the Co-seller payout status section on Settings -> Creator.
The key user-facing states there are:
| UI label | What it means |
|---|---|
Pending transfers | Revenue-share payouts that are still waiting to complete |
Failed transfers | Revenue-share payouts that attempted and did not complete |
Retry transfer | Force another transfer attempt after the underlying issue is fixed |
Pending vs failed transfer states
These two states should be interpreted differently.
| State | What creators should infer |
|---|---|
| Pending | Stripe or the transfer workflow has not finished yet |
| Failed | The transfer could not complete and needs intervention |
Pending is usually a monitor-and-wait state. Failed is an action state.
What Retry transfer does
Retry transfer is not a cosmetic refresh. It triggers a new forced attempt for that failed payout item.
From an end-user perspective, that means:
- the item must still belong to your creator account,
- the app reattempts the transfer for that purchase or invoice,
- you should only retry after the payout destination problem is addressed.
If nothing changed in the co-seller’s Stripe readiness, retrying is likely to fail again.
Purchase vs invoice retry cases
The retry surface supports two kinds of revenue-share items.
| Item type | Plain-English meaning |
|---|---|
| Purchase | A one-time priced-post purchase that owed a co-seller share |
| Invoice | A recurring subscription invoice that owed a co-seller share |
The creator does not need to care about the internal API distinction day to day, but it explains why some failed transfer rows are tied to one-time sales and others to subscription billing.
What to fix before retrying
Before retrying, the creator should verify the co-seller’s payout setup is actually ready.
The practical checklist is:
- confirm the co-seller finished Stripe onboarding,
- confirm the co-seller account is not still in an action-required state,
- then retry the failed transfer row.
That is the correct recovery order. Fix first, retry second.
Related docs
See it in action
Previous
Creator Dashboard Subscriber Health and Payout Queues
How to read the creator dashboard’s subscriber-health cards, recent subscriber rows, pending payout surfaces, failed transfer surfaces, and account-status actions.
Next
Creator Dashboard Buyer Purchase History
How to read the Your recent purchases section on the creator dashboard and what hosted-by, on-demand, and purchase-status rows tell the user.