Skip to main content

Payout rhythm and status of your earnings

ou receive one payout each month. Earnings for a session are released only after the 2-business-day dispute window for that session has passed and only if the session is validated before the monthly cut-off.

Updated over 3 months ago

How payouts work (step by step)

  1. Customer pays upfront
    The session or package is paid at the moment of booking.

  2. You deliver the session
    Coaching takes place as planned.

  3. 2-business-day dispute window
    After each session, customers have two business days to report issues (for example the session didn’t happen, major technical problems, or serious quality concerns).

  4. Session validation
    If no complaint is filed during the dispute window, the session is automatically marked as validated and the net amount (session price minus Yumi42’s commission) is added to your internal coach balance.

  5. Monthly payout on the 5th
    On the 5th of every month, all validated earnings that passed the dispute window before the monthly cut-off are transferred to your bank account via Stripe Connect.

    • Processing Date: The payout is processed on the 5th of every month. If the 5th falls on a weekend or a public holiday, the processing will occur on the next business day.

    • Fund Arrival: The funds are typically credited to your bank account 1 to 3 business days after the payout processing date (the 5th), depending on your bank's processing time.


Monthly cut-off explained (Option B)

To avoid timezone inconsistencies, the monthly payout uses a clear cut-off:

  • Only sessions validated before the 5th are included in that month’s payout.

  • Sessions validated on the 5th or later move to the next month’s payout.

This ensures simple, predictable payout scheduling for all coaches.


Examples

Example 1 — Included in next payout

  • Session: 3 April (Wednesday)

  • Dispute window ends: 5 April (Friday)

  • Validation date: 5 April

  • Cut-off rule: validations on or after the 5th are excluded

  • Payout date: 5 May

Example 2 — Included in same-month payout

  • Session: 29 April (Tuesday)

  • Dispute window ends: 2 May (Friday)

  • Validation date: 2 May

  • Cut-off: validation is before the 5th

  • Payout date: 5 May

Example 3 — Moves to next month

  • Session: 4 May (Saturday)

  • Dispute window ends: 7 May (Tuesday)

  • Validation date: 7 May

  • Cut-off: validation is after the 5th

  • Payout date: 5 June

Example 4 — Dispute filed

  • Session: 10 June

  • Customer reports an issue on: 11 June

  • Session is placed “under review”

  • Validation happens only after Yumi42 resolves the case

  • Payout date depends on resolution timing and cut-off


What must be completed for a payout

A session will be included in the payout if:

  • the session took place

  • the dispute window has ended

  • the session was validated before the monthly cut-off

  • there is no unresolved issue or refund request

  • your Stripe KYC is fully completed

  • the amount is above any minimum payout threshold (if applicable in your region)


How to track your payout status

In your Coach Dashboard you can see:

  • validated earnings

  • earnings still in dispute window

  • sessions under review

  • your upcoming payout amount

  • your past payouts (with Stripe references)


Why payouts are not instant

This short delay protects both you and your customers:

  • prevents fraud, no-shows and accidental double payments

  • reduces chargebacks and reversals

  • ensures stable, reliable payout processing

  • gives customers a fair chance to report serious issues

Instant payouts would significantly increase risk for everyone and are not supported by Stripe’s dispute rules.


Possible reasons for payout delays

Your payout may be postponed if:

  • your Stripe KYC is incomplete

  • a session is still in its dispute window

  • a complaint or refund review is ongoing

  • Stripe requires additional verification

  • the validation happened after the cut-off

  • your total balance does not reach the minimum threshold

Did this answer your question?