What Payment Info Can a Creator See When You Pay Them?

When you pay a creator on FanBell, they see the name or @social handle and email you entered at checkout, the amount paid, and which offer you bought. They never see your full card number, your card's security code, or your bank account — those stay with Stripe, the payment processor. FanBell's own checkout form does not ask for a billing address, though Stripe's card form still collects a postal code in some countries.

What a creator can and cannot see: field-by-field comparison

A FanBell creator sees four things about your purchase: the name or @social handle you typed, your email address, the amount paid, and the offer you bought. Your full card number, security code, and bank account never reach the creator. The table below maps each checkout field to who holds it and whether a creator can view it.

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).

Stripe's handling of card fields is a certification requirement rather than a FanBell promise. A PCI-certified auditor has evaluated Stripe and certified it to PCI Service Provider Level 1, the highest of the four PCI DSS validation levels and what Stripe calls "the most stringent level of certification available in the payments industry" (Stripe, Security at Stripe).

What does a creator see about you after you pay on FanBell?

A FanBell creator sees the name or @social handle you typed at checkout, the email address you used, the amount charged, and which offer you bought — a Paid Private Question, a Shoutout, a Creator Service, a Tip, or a Wishlist contribution. That information sits on the single order tied to that purchase, not on a browsable customer profile.

FanBell describes the fan side of a purchase as "checking out as a guest by card, with no account to create and no app to install," with the request landing "in your creator inbox as a private thread" (how it works). A guest checkout of that shape asks for two identity fields before payment — an email for the receipt and a name or @social handle — and no mailing address or phone number. Whatever you type into those two fields is exactly what appears on the creator's side, so a handle entered instead of a legal name is the only name the creator ever sees. Knowing what that checkout collects is one part of the question; confirming a creator's payment page is legit before you type anything into it is the other.

Does a creator see your full card number or security code?

No to both. Card entry happens on Stripe's own hosted checkout page rather than on FanBell's servers, so the raw card number never reaches FanBell or the creator, and the three- or four-digit security code is discarded after authorization rather than stored — the same reason entering card info on a small creator's page doesn't depend on how big that creator's audience is. FanBell's privacy policy states: "Payments are processed by Stripe. We do not store full card numbers".

"Your customers' card information never touches your servers." — Stripe, PCI compliance guide

Stripe encrypts every stored card number at rest with AES-256 and keeps the decryption keys on separate machines, in an isolated hosting environment that shares no credentials with Stripe's API or website. Stripe adds that none of its own internal servers can obtain plain-text card numbers, which is a stricter boundary than anything a merchant dashboard could enforce on its own.

The three- or four-digit security code is governed by an industry rule rather than by any single company's policy. PCI DSS Requirement 3.3.1.2 strictly prohibits storing card verification codes after authorization, even if encrypted (PCI Security Standards Council, FAQ on card-verification codes). That prohibition sits inside a standard that was recently tightened rather than a legacy rulebook: the PCI Security Standards Council reports that of the 64 new requirements added in PCI DSS v4.x, 51 were future-dated and became effective on 31 March 2025.

"It is not permitted to retain card verification codes once the specific purchase or transaction for which it was collected has been authorized." — PCI Security Standards Council, FAQ 1574

One honest nuance is worth stating plainly. Because FanBell charges run on the creator's own connected Stripe account, a creator who opens their embedded Stripe payments view sees the processor-level record for that sale (Stripe, Connect embedded payment details component) — the same merchant-side detail any shop sees for its own transactions, which for card payments includes the card brand and the last four digits. Even that view is capped by the standard: PCI DSS v4.0.1 Requirement 3.4.1 states that the BIN and the last four digits are the maximum number of digits that may be displayed (PCI Security Standards Council, PCI DSS v4.0.1). The full card number, the security code, and your card's authentication data appear in neither FanBell's records nor the creator's Stripe view.

Does Stripe collect your billing address or ZIP code at FanBell checkout?

FanBell's own checkout form never asks for a billing address. Stripe's card form can still ask for a postal code, because FanBell does not override Stripe's default setting. Stripe's API reference documents that default as auto, under which "Checkout will only collect the billing address when necessary" (Stripe, Create a Checkout Session).

In practice, Stripe's auto billing-address setting behaves differently by region. Stripe's changelog entry dated 30 September 2025 records that a postal code is no longer collected for card payments on Checkout and Payment Element in exactly three regions — Canada, the United Kingdom, and Puerto Rico — where previously it was always collected under the auto setting (Stripe, changelog 2025-09-30). A US card payer should therefore still expect Stripe to ask for a ZIP code on the card form. Any postal code you type is collected by Stripe for card verification and does not appear on the creator's FanBell order record. "FanBell does not ask for a billing address" is therefore a statement about FanBell's own form, not about Stripe's card form.

What does a creator see when you send a Paid Private Question?

A creator sees the text you write, plus the same order fields attached to every FanBell purchase: name or @social handle, email, and amount. Paid Private Questions are text-only on the fan side — the fan sends a written question and the creator replies by text or voice, with no file or image upload in the question box.

Because there is no attachment field, there is nothing for a creator to open beyond what you type into the question box. A creator configures only two things on a Paid Private Question, the price and the reply time, and can decline and refund a question rather than answer it.

What does a creator see for Creator Services or Personalized Shoutouts?

A creator sees whatever you voluntarily attach to the request, on top of the same four order fields. Creator Services and Personalized Shoutouts carry files in both directions: a fan can attach a track, resume, or screenshot when ordering, and the creator delivers a written note plus files or a private link for anything larger.

FanBell documents the exact delivery envelope for a Creator Service: a written note plus up to 5 files — video, audio, images, PDF, Word, Excel, or PowerPoint, with video and audio up to 20 minutes — and optionally a private link for anything larger. Turnaround is set by the creator rather than by FanBell, and FanBell's own guidance frames a clear delivery window such as 3–5 days as the workable norm.

A file you attach is a difference in what you voluntarily submit, not a difference in payment data. A resume uploaded for a service review is content you chose to share for that specific request — it is not card or billing information, and a creator can decline and refund a request that falls outside what they scoped.

Can a creator see your other FanBell purchases or payment history?

No. A FanBell creator sees only the orders placed with them, tied to the specific thread or request. A creator cannot see whether you tipped or purchased from a different creator on FanBell, and no running profile of your platform-wide spending appears anywhere in the creator inbox that FanBell gives each creator. That same order record is also what typically counts as evidence in a payment dispute if a charge is ever contested.

FanBell describes that inbox as per-creator and per-thread: "Every paid interaction lands in one creator inbox: private threads for questions and services, delivery status for shoutouts, project support progress". FanBell's privacy policy adds three published rules that keep a thread scoped to the two people in it — "Private request threads are accessed through a secure, unguessable token link tied to the fan's email," "A fan's email is never shown publicly," and anonymous fan wall entries display as "Anonymous Fan".

Does a creator see your bank account or payout details?

No, and no bank detail of yours ever enters the flow. As a fan you pay by card at checkout and are never asked for an account or routing number. Bank details exist only on the creator's side of the transaction, where a payout account is required to receive money rather than to spend it.

FanBell states that it "pays out to your bank account through Stripe" and that a creator connects that account "once during setup" — a step that happens in the creator's own Stripe onboarding, entirely separately from any fan's card. Stripe says it treats bank account information much as it tokenizes card numbers, holding it in an isolated environment whose access is restricted to a small number of specially trained engineers and reviewed once every quarter. For the creator-side version of the question, see is it safe to share your bank details to get paid as a creator.

Who besides the creator can see your payment information, and which fields do they get?

Four parties touch part of a FanBell payment, and each receives a different slice: FanBell holds the order record, Supabase stores that record and any uploaded files, Stripe handles the card fields, and Resend delivers the transactional email. No advertiser, data broker, or other creator sits anywhere in that chain.

FanBell's privacy policy states: "We share data only with the processors needed to run the service: Supabase (database, auth, storage), Stripe (payments and payouts), and Resend (email). We do not sell personal data".

Of FanBell, Supabase, Stripe, and Resend, only Stripe is a card payment processor: Supabase is a database and storage provider and Resend is an email provider, so neither ever receives card data. Supabase publishes that it is SOC 2 Type 2 compliant and that Enterprise and Team customers can access its SOC 2 Type 2 report from the dashboard. Stripe protects the payment fields in transit as well as at rest — Stripe mandates HTTPS with TLS for all services and automatically blocks requests made using anything older than TLS 1.2.

The accurate claim about who sees a FanBell payment is therefore narrower than "nobody else" and also narrower than "three processors see everything." Beyond those four parties, FanBell's terms add that FanBell may cooperate with Stripe, card networks, law enforcement, or rights holders where appropriate. No other creator, brand, advertiser, or data buyer appears anywhere in that list. A checkout that runs through a named processor, shows the creator's real page, and never asks you to pay outside the flow is the basic signal worth checking — see FanBell's safety page for the fuller checklist.

Frequently asked questions

Six questions come up most often about FanBell fan checkout: whether a creator sees your card's last four digits, whether they see your other purchases, whether a mailing address is collected, whether Stripe asks for a ZIP code, whether a handle can replace a legal name, and whether card details reach a creator's bank.

Does the creator see my card's last four digits?

Not in FanBell. FanBell's privacy policy states that FanBell does not store full card numbers, and FanBell's order records and creator inbox hold no part of your card number. Because the charge runs on the creator's own connected Stripe account, a creator opening their embedded Stripe payments view sees the standard merchant-side payment record for that sale, which for card payments includes the card brand and last four digits — the same detail any shop sees for its own transactions. PCI DSS v4.0.1 Requirement 3.4.1 caps that display at the BIN and last four digits (PCI Security Standards Council).

Can a creator see other things I've purchased on FanBell?

No. A FanBell creator sees only the order or thread tied to the specific purchase you made with them, never your activity with other creators on the platform.

Does the creator see my physical mailing address?

No. FanBell's guest checkout collects an email and a name or @social handle, not a mailing address, and FanBell does not handle physical shipping for any offer.

Will Stripe ask me for a billing ZIP code?

Probably, if you are paying with a US card. Stripe's Checkout default is auto, which "will only collect the billing address when necessary", and Stripe stopped collecting a postal code for card payments in Canada, the United Kingdom, and Puerto Rico as of its 30 September 2025 change. Any ZIP you enter goes to Stripe, not to the creator's FanBell order record.

What if I don't want to use my real name at checkout?

You can enter a name or @social handle instead of your legal name — that is exactly what the "Name or @social" field is designed for, and whatever you enter there is what the creator sees.

Does FanBell share my payment details with the creator's bank?

No. A creator's bank account is connected separately through their own Stripe payout setup and has no link to your card details as a paying fan; Stripe handles the two in entirely separate steps.

Paying a creator directly doesn't have to mean guessing what they can see about you. Create your free FanBell page and every fan checkout on it follows the same rule: name or handle, email, and amount only — nothing more.