Skip to content
EntryWick documentation

For an owner, once, usually because a paid registration refused to take money.

Payouts settings — admin

Who opens it: an owner, once, usually because a paid registration refused to take money.

What they came to do: connect the account the money arrives in, and understand where it goes.

True when they leave: either Stripe can take payments for them, or they know exactly what Stripe is still waiting for.

Decisions already made

  • Onboarding is Stripe's (Express, ADR-013). We never see bank details and never hold funds — which the page says in plain words, because "where does the money sit" is the first thing an organizer asks.
  • Opening the page does not call Stripe: it shows what Stripe last told us, and "Refresh status" asks. An admin screen that fails because a third party is slow is a bad screen.
  • "Connected" means charges_enabled — it can take money — not merely that an account row exists. An account can look finished while Stripe is still waiting on documents.
  • A paid registration form refuses before reaching Stripe when the account is not ready: "finish onboarding first" is a better answer than a failed card.

Open questions

  • Nothing surfaces why Stripe is waiting (it knows: documents, bank account, tax id). Express gives a dashboard link; is that enough, or should we read the requirements list?
  • Per-event payout accounts are not supported (one per tenant). A regional body running groups' own events may want them.
  • No display of the platform fee an organizer will pay. They can read it in pricing, but here is where they wonder.