BOTLOBBIESWhat information is shared with Stripe when I open a payment?
Stripe processes the payment, and the service sends purchase or subscription information needed to associate it with the intended bot. The checkout code also includes bot or player references and some names in metadata; the privacy page says the website does not receive your complete card details.
Separate card entry from purchase references
A payment provider needs to know what purchase is being completed and where to return the customer afterward. The service creates Stripe checkout or billing sessions containing the selected plan, amount-related information, and references used to reconcile the result. This is different from asking you to type a full card number into a bot command or support message. Read the actual Stripe payment screen before confirming. Its displayed terms describe the purchase you are authorizing, while the website later checks the corresponding result.
Do not assume the checkout is anonymous
The implementation can attach checkout identifiers, bot identifiers, associated Epic identifiers, bot nicknames, or player names to purchase metadata. That helps connect a confirmed payment with the right service record. Consequently, a statement that the website does not receive a complete card number should not be expanded into Stripe receives no account-related information. The exact fields depend on the supported purchase flow. Keep that distinction in mind when deciding which account and bot you intend a checkout to activate or renew.
Ask payment questions without exposing payment secrets
For a payment problem, use the official billing controls or support contact and describe the time, plan, result, and visible reference where appropriate. Never send a complete card number, security code, password, or private account authorization file. Do not post a full checkout address publicly merely to show that a session exists. If you have a data question concerning the payment provider as well as the website, distinguish those two recipients instead of assuming one local account action automatically changes all provider records.