Payment and Provider Disclosure

Document status

This disclosure must be reviewed before production payments. It documents current product intent, not final legal terms.

Provider availability can differ by environment, account readiness, and validation status.

Who does what

PedalaPlay coordinates the product experience and membership/access state. External providers process specialized parts of the flow.

• Stripe processes the primary card recurring payment path and connected-account flow.
• Pagar.me may process Pix invoices when the Pix flow is enabled and validated.
• Discord and WhatsApp support communication/access workflows; they do not define payment truth inside PedalaPlay.

Stripe card recurring

Stripe card recurring is the primary launch lane for paid membership. Access should update through webhook-confirmed subscription state.

Stripe fees, connected-account readiness, restrictions, disputes, and settlement timing may affect organizer operations.

Pix validation status

Pix is provider-backed but public exposure depends on a fresh validation pass. Pending confirmation should be shown clearly to players and organizers.

If provider-backed Pix confirmation is not clean, PedalaPlay should keep Pix in controlled beta, manual flow, or hidden state.

Payment state and access

PedalaPlay controls product access based on local membership and provider-confirmed payment state.

Provider dashboards may contain operational details, but normal users should see clear product states such as active, pending, past due, canceled, or needs attention.

Discord and WhatsApp

Discord can help maintain community access and channel coordination, but it is not the product source of truth for membership or billing.

WhatsApp is optional, paid, quota-controlled, and transactional only. It requires player opt-in and approved templates, and it must not be used for groups or marketing in this launch scope.