Set up payouts

Tips lives under MONETIZE in the Pyre.Stream sidebar, and everything about the tip itself is documented once, in Tips: the form your viewers fill in, the presets, the goal picker, the monthly option, the thank you message, the alert that fires and the leaderboards it feeds. None of that is different here.

This page is the other end of it. Where the money goes, how you set that up without leaving Pyre, and what happens in the meantime.

Two rails, two cards

The Tips page carries two payout cards, and they are independent. Payouts is Stripe and it carries card payments. PayPal is one field and a button, and it carries PayPal payments. You can run either, both or neither, and a viewer is offered whichever ones are ready.

What is true of both: the money settles into an account of yours. Pyre never holds it, there is no Pyre balance to withdraw from later, and you are the merchant of record on every tip you take, which is why refunds, disputes and tax documents all sit on your own account.

The Payouts card shows your status and nothing else about the account, not even a masked account number. Its head pill is the whole state in two words: Not set up, Setup unfinished, Action needed when Stripe has bounced something back, and Payouts active, which is the only one that means card money can move.

Before you start, the card’s own line tells you where the setup will happen: Take card tips straight into your own Stripe account. Setup opens right here in Pyre. Once you are done it changes to Connected. Card tips go directly to your Stripe account, and payouts follow your Stripe schedule.

Set up payouts

Three steps, and the middle one is Stripe’s. The card takes itself over in place, so nothing navigates away, and closing it loses nothing.

The first step names what you are about to do: Set up payouts. 2 minutes, right here.

1. Before you start. Expectations, not fields. You are creating your own Stripe account, in your name, and it is where your card tips land. Three things are asked of you and the step names all three up front:

   What Stripe needs	Why
   Your legal name and date of birth	Stripe checks who is being paid. Business accounts add the company details.
   A bank account	Where your payouts land. You can change it later without redoing this.
   About 2 minutes	Most creators finish in one sitting.

   It closes on the promise that makes the rest of it safe to start: Stop any time. Nothing is lost, and you pick up where you left off.

2. Verify your details. The body of this step is Stripe’s own form, rendered inside the Pyre page and themed to look like the rest of it. Pyre does not rebuild those fields and does not read them: Stripe collects this directly. Pyre never sees your ID or your bank number.

   What Stripe asks for depends on your country and on whether you are paid as a person or as a business, so the fields are Stripe’s decision rather than a Pyre form with a fixed shape. The Continue button belongs to Stripe, and so does the “Powered by Stripe” line under it, which cannot be removed.

   Leaving mid form is fine: Close this any time. Stripe keeps what you entered and you resume from the same place.

3. Done. The last step reads your account back from the server, never from something the browser assumed, so Payouts active means Stripe has said so: Stripe finished checking your details. Nothing else is waiting on you.

   It answers two questions and then sends you on. Where tips go is your own Stripe account, because every card tip settles there and Pyre never holds the money. When you get paid is Stripe’s standard schedule: Payouts arrive on Stripe's standard schedule, typically 2 business days.

   Then it points at where the money lives from now on: Revenue holds your payments, payouts, balances, disputes and tax documents, all inside Pyre. Come back to this card only to change how you get paid.

Stripe opens one sign-in window, and the first step says so

A pop-up nobody warned you about reads like something broke, so the journey names it before it happens: Stripe opens a small sign-in window once to verify it is you. The rest happens right here.

That window is Stripe’s own, it sits on a connect.stripe.com address, and it is a code sent to your email. It is not removable: Stripe runs the sign-in because Stripe carries the risk on these accounts. It is the one part of the setup that is not ours to draw, and everything on either side of it is the page you were already on.

Nothing in Pyre shows your bank details back to you

No screen in Pyre displays your payout account, not even as a masked number: the stored reference is encrypted and has no read path. To see or change which bank account you are paid into, use Stripe’s own payouts view in Revenue. That is why the last step offers to change how you get paid rather than showing you what it is today.

This is the same three step journey the Pyre.Bot portal runs, on the same account, and that is deliberate rather than an accident of two teams. A creator who lives in Pyre.Bot is never handed the smaller version.

Tips can be on before Stripe is done

Tips do not wait for Stripe. Switch them on, share your page, and finish the payout setup when it suits you. The Tips page gives you two prompts about it, both inside the Payouts card, and neither one blocks anything.

Before there is an account, the card’s own row is the invitation: Set up payouts. 2 minutes, and it opens right here in Pyre. with Card tips settle straight into your own Stripe account. Pyre never holds the money. under it, a Start setup button, and the reassurance that you are not trading one for the other: Tips stay on while you set this up. Card tips are recorded and land once your account is ready.

Once card tips have come in and payouts are not ready yet, the same card reads You have tips waiting. / Finish payout setup to receive them. with a Finish setup button.

The waiting prompt shows no amount, deliberately

Its hint is Recorded by Pyre. Your Stripe balance opens once setup is done. and there is no figure anywhere in it. A number on a payout prompt would read as a balance Pyre is holding for you, and Pyre holds nothing, so the prompt is a yes or no rather than a total. Real figures come from Stripe, in Revenue, once the account is live.

It is also card only: a creator taking PayPal tips and no card tips never sees it, because PayPal money is already in a PayPal account and nothing is waiting on Stripe.

You are prompted once, never twice. Where the journey runs, the older page banner that said tips were on without a payout account steps aside and the card carries the whole nudge. Requirements Stripe raises later are a different matter: those stay on Stripe’s own banner at the top of the card, with its Add information button, because Stripe is the only surface that knows exactly which detail is missing. Alongside it, the page keeps one banner of its own for the window before Stripe’s banner has anything to draw: Your payout setup needs attention.

That banner has two forms, and the better one is the one that names the fields. When Pyre knows which requirements are outstanding you get Stripe still needs: <the fields>. Viewers cannot tip you until this is done., with the missing details listed out. When it does not, it falls back to the general Stripe needs more information before you can receive tips. Either way the Finish setup button beside it is the way back in.

When the setup cannot open in Pyre

Embedded Stripe needs a key that a deployment either has or does not. Where it is missing, the Payouts card falls back to its plain Stripe row and a Connect Stripe button, which opens Stripe’s own onboarding in a new tab and returns you here. The card’s line changes to match: Take card tips straight into your own Stripe account. Onboarding opens with Stripe in a new tab.

That path is permanent, not a broken version of the first one, and the swap is honest in both directions: the journey’s “it opens right here in Pyre” is never shown on a page that cannot deliver it, and the new tab is never promised on a page that can.

Whose setup this is

The Payouts and PayPal cards are owner only, enforced at the server rather than only in the interface. A platform operator acting on your channel gets a refusal instead of your payout form, and so does a moderator at every access level, including the highest. Nobody starts, finishes or changes another person’s payout setup.

The status stays readable in those sessions, so somebody helping you can see that payouts are unfinished without being able to act on it. See Give a moderator access.

Where your money lives afterwards

Once Payouts active shows, this card is finished with you except when you want to change how you get paid. Your payments, your payouts, your balances, your disputes and your tax documents are all in Revenue, inside Pyre, and none of it sends you to a Stripe dashboard.