Skip to content

Tips

A tip is a viewer sending you money from your public page. Pyre gives you the page, the form on it, the alert that fires when somebody uses it, and the goal bar it fills.

Your public profile is your tip page. There is no second address to share: pyre.studio/s/your-handle carries your links, your live status and the tip form in one document.

Tips lives under Monetize in the sidebar and is yours alone. It never appears on a channel you moderate, and no access level reaches it, because money is one of the things that stays structurally with the channel owner. See Give a moderator access.

Tips are off until you turn them on. A creator who has never opened this page has a public profile with no tip form on it.

The card is titled Send a tip, and this is the whole form:

  • Choose an amount, your preset buttons. One is already selected when the page opens, so a viewer who agrees with your middle preset can pay in two clicks.
  • Custom amount, for anything else. Typing here clears the preset.
  • Where should it go?, a goal picker, but only if you have tip goals running. It always offers General support as the default, so nobody is forced to aim their money at a goal.
  • Your name, up to 80 characters.
  • Message (shown on stream), up to 200 characters, with a row of emoji to drop in.
  • Make it monthly, only if you allow recurring tips.
  • Payment method: Card or PayPal. The row is hidden when only one is available, because a choice of one is not a choice.

The submit button reads back the decision as it is made: Send a tip becomes Tip $5, and then Tip $5 toward whichever goal they picked.

There is no anonymous checkbox. Leaving Your name blank is how a viewer stays anonymous, and the placeholder says so by reading “Anonymous”. A blank name is stored as the word Anonymous, which is why your leaderboard can show one Anonymous row standing for several different people.

When the payment goes through, the viewer comes back to your page and gets a Thank you for the support! banner with your own thank-you message quoted underneath it. It shows once and then clears itself from the address bar.

  1. Open Tips in Pyre.Bot. The settings live in the Tip settings card.

  2. Turn on Accept tips on your public page. This is the switch that puts the form on your profile. Nothing below it matters while this is off.

  3. Decide on Allow monthly (recurring) tips. It starts on. Off, and the Make it monthly toggle never appears for viewers.

  4. Pick your Currency. Six are offered: USD, EUR, GBP, CAD, AUD and DKK.

  5. Set your Minimum tip. It starts at 1.00.

  6. Set your Preset amounts, comma separated, up to 8 of them. They start at 2.00, 5.00 and 10.00. The hint under the field is doing real work: anything you type below your minimum is raised to the minimum rather than rejected, so a preset list can quietly come back different from what you entered.

  7. Write your Thank-you message, up to 280 characters. This is what a viewer reads after paying.

  8. Save. The two toggles are part of the form, so flipping one and navigating away changes nothing.

  9. Connect a payout account. Money has to land somewhere. There are two cards for this, Payouts and PayPal, and they are covered below.

The settings pane deliberately has no bio and no socials fields. Those moved to Public profile, which is the other half of the same page.

Two independent rails, one card each, directly under the settings. You can run either, both, or neither, and a viewer is offered whichever ones are ready.

The Tips page with the Tip settings card on the left, Accept tips off and Allow monthly tips on, currency USD, minimum 1.00 and presets 2.00, 5.00, 10.00, and on the right a Payouts card reading Stripe is still reviewing your details above Stripe's own Add information banner, a PayPal card marked not connected with an empty PayPal email or Merchant ID field and a Connect PayPal button, and the start of a Tip goals card

Pyre takes a 0% cut on both rails. A tip settles into your own account: Pyre never holds the money and there is no Pyre balance to withdraw from later, which is why each rail needs an account of yours attached before it can carry anything. You are the merchant of record on every tip you take, so refunds, disputes and tax documents all sit on your own account rather than on ours.

This card is Stripe, and it is the card rail. It shows your account status and nothing else about the account: no account number, no reference, not even a masked one. What fills the rest of the card is either the setup journey, described in Set up payouts below, or Stripe’s own view of a finished account.

The pill in the card head is the status in two words, and there are three of them. Under the pill, in the resting card, sits the longer sentence for the same account, and the four sentences do not map one to one onto the three pills:

PillThe sentence under it
Not set upNo payout account yet.
Setup unfinishedStripe is still reviewing your details. while Stripe is checking, or Stripe needs more information before it can pay you out. when it has come back wanting something
Payouts activeReady to receive payouts.

Payouts active is the only one that means card money can move. Stripe asking for more details is Setup unfinished in the portal rather than a pill of its own, so the sentence is the part that tells you which kind of unfinished you are looking at. The Pyre.Stream card splits that out into a fourth Action needed pill, which is the one place the two shells deliberately differ.

When Stripe wants something from you, Stripe’s own banner appears at the top of the card with an Add information button. That button is Stripe’s flow rather than ours, and it is the one surface that lists exactly which details are outstanding.

Setup happens inside this card. Where a deployment cannot embed Stripe, the same card falls back to a button that says so plainly: Opens Stripe in a new tab and brings you back here when you are done. The button reads Set up payouts the first time and Continue payout setup once an account exists, so it never invites you to start something you are already in the middle of. That second path is permanent rather than a broken version of the first, and the card never promises “right here in Pyre” on a page that cannot deliver it.

You can turn tips on before any of this is finished, deliberately. See Tips can be on before Stripe is done.

Type your PayPal email or Merchant ID, press Connect PayPal, and that is the whole setup. There is no review step and no onboarding round trip, so a connected account can take PayPal tips immediately.

Both cards are owner only, at the server and not just in the interface. A platform operator acting on your channel gets a refusal rather than your payout form, and so does a moderator at every access level. 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, but every button that would act on it answers with a refusal.

Three steps, and the middle one is Stripe’s. The whole thing happens inside the Payouts card: it takes the card over in place, and closing it never loses anything.

The step you start on says what it is: Set up payouts. 2 minutes, right here.

  1. Before you start. What the first step is for is 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 card names all three before you begin:

    What Stripe needsWhy
    Your legal name and date of birthStripe checks who is being paid. Business accounts add the company details.
    A bank accountWhere your payouts land. You can change it later without redoing this.
    About 2 minutesMost creators finish in one sitting.

    The step ends on the honest note: Stop any time. Nothing is lost, and you pick up where you left off.

  2. Verify your details. This step’s body is Stripe’s own form, rendered inside the Pyre page. Pyre does not rebuild it and does not read it: Stripe collects this directly. Pyre never sees your ID or your bank number.

    Which fields you get is Stripe’s decision, not ours, and it varies by country and by whether you are being paid as a person or as a business. The Continue button in there is Stripe’s, and so is the “Powered by Stripe” line under it, which cannot be removed.

    You can walk away mid form: 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 rather than from anything the browser guessed, so Payouts active means Stripe has actually said so: Stripe finished checking your details. Nothing else is waiting on you.

    It tells you two things and then gets out of the way. Where tips go is your 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.

Tips do not wait for Stripe. You can switch them on, share your page and finish the payout setup later, which is the whole point of doing the setup this way round.

You get two prompts for 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 hint that answers the question you actually have, which is whether switching tips on now costs you anything: Tips stay on while you set this up. Card tips are recorded and land once your account is ready.

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

One prompt, never two. The older banner that said tips were on without a payout account retires wherever the journey runs, so you never read the same sentence twice on one page. It survives on the fallback path, where there is no journey to carry it.

Once your payout setup is done, the Your money card is where the rest of your money life happens. It sits between the two rails, directly under Payouts and above PayPal, and that position is the scope: every panel in it is Stripe’s own view of card money, marked Live from Stripe, and none of it covers your PayPal tips. Putting it below PayPal would have read as covering both rails, which it does not.

TabWhat it shows
PaymentsEvery card tip Stripe has settled for you, with its status.
PayoutsThe transfers Stripe has sent to your bank, and the ones on the way.
BalancesWhat is available now and what is still pending in your Stripe balance.
DisputesEvery card tip a viewer has challenged, and what Stripe needs from you to answer it.
Tax documentsThe tax forms Stripe has issued for your payouts. Download any of them here.

Two of those tabs carry a line under them, and both lines are the point rather than decoration.

On Disputes: You are the merchant of record, so a dispute is between you and the card holder. Pyre never holds the money and cannot answer one for you. Opening a row expands Stripe’s own evidence form in place, and the answer you write goes to Stripe.

On Tax documents: Pyre does not file anything for you and does not give tax advice. These are your account's documents, shown where the rest of your money lives. Forms appear when Stripe issues them, on Stripe’s calendar rather than on a Pyre one.

Before your setup is finished the block is closed rather than empty: Your payments, payouts, disputes and tax documents appear here once your payout setup is done. That is not a failure state. Opening one of those panels asks Stripe for a session, and asking for a session is what creates an account, so a creator who has not started must not be able to start by clicking a tab.

If a panel itself will not render you get Stripe could not render this panel. Try another tab, or reload the page. and the other tabs keep working.

Four things, and only one of them needs setting up first.

An alert fires. Out of the box, with no configuration at all: an alert you have never touched is treated as on, with no minimum. The default template is {name} just tipped {amount}!. Everything about it, the sound, the image, the animation and the wording, is on the Alerts page under the Tip row.

It gets read aloud. Tips are one of the event types text to speech reads by default, and what it reads is the viewer’s message. Spoken text is cut at 300 characters and a viewer can only type 200, so a plain tip message is never cut off. Adding the tipper’s name to your read format is what can push one over.

Your goals advance. A tip goal is a goal bar widget, so it is not configured here. The Tip goals card on this page says as much and points at Overlays & Widgets. If a viewer picked a goal on the form, only that goal moves. If they did not, every matching goal does.

It is counted. Recent tips and Top supporters this month on this page both fill in without you doing anything.

If you want a tip to have to clear a floor before it interrupts your stream, set Minimum amount (cents) on the Tip row of the Alerts page. It starts at 0, meaning every tip fires.

Honest limits, so you do not go looking for them:

  • The bot does not post in chat when a tip lands. The alert is on your overlay, not in your chat. Nothing ships that announces a tip to chatters.
  • There is no !tip command. No built in command posts your tip page address, and there is no tip variable for a custom command. Your profile URL is the link, and you share it yourself.
  • A tip does not award loyalty points. A tipper is a payment, not a chat identity, so there is no viewer balance to credit. Points come from chat. See Loyalty and giveaways.
  • You cannot create or edit a goal here. Only see that they exist and be told where they live.
  • There is no tip blocklist. A viewer’s message is capped at 200 characters and that is the only filter on it, so the moderation to think about is what your alert and your text to speech do with the words.

Both cards on this page show up to eight rows.

Top supporters this month means the calendar month, counted from the first instant of it. The board on your public page uses the same word for a rolling 30 days, so the two can disagree in the first days of a month. Neither is wrong, they answer slightly different questions, and the public one is the one your viewers see.

Your public page also carries its own leaderboard with ALL, MONTH and WEEK tabs, and it only shows the tabs when at least two of those boards have anybody in them.

Your page has no tip form. Accept tips on your public page is off, or was never saved. A viewer sees a profile with no form and no explanation, so nothing on the page will tell you this. Check the toggle rather than the page.

Your page says it cannot accept tips yet. Tips are on but your payout account is not finished. The Payouts card is where the prompt lives, either as Set up payouts. 2 minutes, and it opens right here in Pyre. or, once tips have come in, as You have tips waiting. Run the three steps in Set up payouts and the page stops saying it.

A viewer says a small amount was refused. Each payment method has its own floor, and setting your minimum to 0 does not lower it. The form handles this itself: when an amount is too small for the card rail but PayPal can still carry it, the viewer is told and offered PayPal.

Your presets came back different. Anything below your minimum was raised to it on save. Lower the minimum first, then set the presets.

A tip landed but no alert fired. Check Minimum amount (cents) on the Tip row of the Alerts page, and check the alert is not explicitly switched off. An alert you have simply never opened still fires.

A renewal alert had a blank name. Expected, and covered above. Rewrite the recurring tip alert so it does not use {name}.