Bans, refunds, and notifications

Block repeat offenders, process refund requests, and get it all pinged to your Discord.

The word filter handles words; these pages handle people.

Bans

The Bans page blocks three things:

Donors - a banned donor can’t tip you any more. Their money isn’t welcome, so it isn’t taken.
Videos - a banned video can never be requested again, no matter who asks. For that one clip you never want to hear again.
Channels - everything a YouTube channel uploads is refused, including videos it posts after you ban it. Paste the channel’s link (youtube.com/@name) or any video from it, or tick Also ban the channel that uploaded it when banning a video.

Banning a video or channel only stops new requests. If copies are already waiting in your media queue, TipPage offers to remove them there and then.

Someone who wants a banned video played can upload the same file again under a new link. TipPage recognises that without downloading anything: when you ban a video it notes the video’s length and the frames YouTube itself publishes from it (and its thumbnail), and every video requested afterwards is compared against them.

A tip whose video looks like a banned one isn’t refused - it goes to your review queue with the banned video beside it, whatever your review switches say, so a mod decides. Card tips are held, not charged, until then. Chat song requests, channel points and API tips have no review step, so a lookalike is refused there with “This video looks like one that’s banned here”.

It catches the common case - the same file reuploaded. A cut or extended version, a mirrored or cropped copy, or a song re-uploaded over a still image with a different length can still get through; ban those as you see them.

Videos TipPage bans everywhere

TipPage staff can ban a video or channel across every channel on the platform (for example flashing-image or doxxing videos). Those are refused on your page the same way, and a reupload of one is held in your review queue labelled as a TipPage ban. They don’t appear on your Bans page and you can’t lift them.

On card tips the money side is clean by design: tips are authorized before they’re captured, so a banned donor’s card hold is released and they’re never actually charged. PayPal can’t hold first - a banned PayPal tip is captured and then refunded, which viewers agree to when tipping.

Bans follow the person, not the card

A ban isn’t one card number. TipPage links the identity signals a tip carries - card identity, receipt email, Twitch or Kick account, device - into one ban, and blocks a match on any of them. When someone tries to slip past with a fresh card, whatever new signals they expose get added to their ban: evading it makes it stronger. Weaker signals (a similar device, a shared connection) never block on their own - they raise a suspected evasion notification instead, so borderline calls stay yours.

Open any donor from your history to see their donor profile: the identities the engine has linked, which tip connected them, and “possibly the same person” neighbours it deliberately shows but never merges.

Want fewer anonymous troublemakers in the first place? Settings → Payments → Donor identity can require sign-in with Twitch or Kick before tipping, and use the signed-in account’s name as the tip name.

Refunds

Two pages, two directions:

Tips is the ledger - every tip you’ve received, whether it was paid by card or PayPal, added by hand, or earned as a sub reward. Refund any paid tip from here, whether or not the donor asked.
Refund requests is where donors ask. It’s off by default; when you turn it on, donors sign in at refund.tippage.com with their receipt email and can request a tip back. Each request shows the tip and the donor’s reason. Approve or reject - it’s your call, and donors agree when tipping that they’re not entitled to a refund.

Refunding from the Tips page

Search by donor name, message or tip reference, filter by paid / refunded / free / blocked, card or PayPal, and a date range. Click a row to open the tip (message, TTS clip, media, donor history), or:

Refund on the row refunds that tip.
Tick several and use the bar at the bottom to refund them all in one go, up to 25 at a time. Each tip is handled on its own, so one that can’t be refunded never stops the rest - you get a per-tip result.

Card tips are refunded immediately, in full. The money comes out of your TipPage payout balance, and if that can’t cover it, from the bank account you registered. (On a legacy Stripe account it comes out of your Stripe balance, right away or as soon as your recent tips settle. If you’ve since moved your payouts into TipPage, a tip from before the move is covered by TipPage instead.) Stripe’s fee and the platform fee aren’t returned, so a refund costs you slightly more than the tip paid you.

PayPal tips go straight to your own PayPal account, so TipPage can’t refund them for you: refund the transaction in PayPal (the row shows the transaction ID to search for), then use Mark refunded so the ledger matches.

Either way the donor gets an email saying you refunded their tip - worded differently from the one they get when a request of theirs is approved. If the same tip had an open request, that request is closed as approved.

Only members with write access to Refunds can see the Tips page: it lists payment references and moves money.

With TipPage payouts there is no Stripe dashboard: the Tips page is where refunds happen. On a legacy Stripe account, a refund you issue from your Stripe dashboard instead is picked up too - the ledger and any open request are updated for you.

Discord notifications

Settings, Webhooks tab: paste a Discord webhook URL and TipPage pings your server when moderation happens. Four event types, each with its own toggle:

Ban attempts - a banned donor tried to tip.
Blocked messages - a tip was blocked by your filter (includes the AI reasoning on TipPage+).
Filtered messages - a message had words replaced.
Banned video requests - someone tried to queue a video from your banned list.

There’s a Test button to check the webhook works.