Bevy Pay lets your community collect paid event ticket revenue through Stripe without a separate merchant account setup. Use this guide for what Bevy Pay supports, how fees and payouts work, and where to connect HQ or chapter payment settings — then open the linked articles for refunds, payout operations, and saved payment methods.
Bevy Pay connects your community site to Stripe so organizers can sell paid tickets and deposit ticket revenue. Bevy handles the payment integration — you do not need a separate merchant account approval process outside Stripe’s own onboarding for the connected account.
| Goal | Where | How-to article |
|---|---|---|
| Confirm HQ unlocked paid ticketing | Admin event types + Bevy Pay for the community | What HQ must enable first; Configure event ticketing |
| Connect chapter Stripe / payment lead | Chapter Dashboard → Settings → Payments | Chapter-level payouts |
| Understand HQ vs chapter payout control | Community payout model | Managing paid events: payouts, refunds, and deleting attendees |
| Refund a paid order | Event → Registrations → Refund total order | Refund a paid ticket |
| Help an attendee update a saved card | Checkout payment step | Saving/updating payment info for ticket transactions |
What Bevy Pay supports
- Bank deposits — ticket funds deposit to a U.S.-based bank account. One bank account can be linked at a time for that connected Stripe account.
- Currencies — Bevy accepts dozens of presentment currencies for ticket prices (see table below). The chapter’s currency setting controls the currency tickets are sold in; checkout does not auto-convert to the purchaser’s local currency.
- Cards — credit cards only today: Visa, Mastercard, American Express, JCB, Discover, UnionPay, and Diners Club.
- Not supported — AliPay, Apple Pay, Google Pay, and other Stripe wallet types are not available for Bevy Pay checkout.
Note: International card transactions may incur Stripe’s international fees. Bevy’s processing fee percentage stays the same regardless of where the purchaser is or which presentment currency you use.
Supported currencies
| USD | CHF | HRK | MMK | RSD | VND |
| AED | CLP | HTG | MNT | RUB | VUV |
| AFN | CNY | HUF | MOP | RWF | WST |
| ALL | COP | IDR | MRO | SAR | XAF |
| AMD | CRC | ILS | MUR | SBD | XCD |
| ANG | CVE | INR | MVR | SCR | XOF |
| AOA | CZK | ISK | MWK | SEK | XPF |
| ARS | DJF | JMD | MXN | SGD | YER |
| AUD | DKK | JPY | MYR | SHP | ZAR |
| AWG | DOP | KES | MZN | SLL | ZMW |
| AZN | DZD | KGS | NAD | SOS | |
| BAM | EGP | KHR | NGN | SRD | |
| BBD | ETB | KMF | NIO | STD | |
| BDT | EUR | KRW | NOK | SZL | |
| BGN | FJD | KYD | NPR | THB | |
| BIF | FKP | KZT | NZD | TJS | |
| BMD | GBP | LAK | PAB | TOP | |
| BND | GEL | LBP | PEN | TRY | |
| BOB | GIP | LKR | PGK | TTD | |
| BRL | GMD | LRD | PHP | TWD | |
| BSD | GNF | LSL | PKR | TZS | |
| BWP | GTQ | MAD | PLN | UAH | |
| BZD | GYD | MDL | PYG | UGX | |
| CAD | HKD | MGA | QAR | UYU | |
| CDF | HNL | MKD | RON | UZS |
- Set chapter currency in chapter Settings (Payments / currency controls for that chapter).
- Ticket prices and checkout use that chapter currency — not the purchaser’s browser locale.
Invoices, VAT, and tax documents
- Bevy Pay does not send a separate tax invoice for ticket purchases.
- Use the ticket confirmation email and the attached ticket PDF as source documents when you generate invoices off-platform.
- The ticket PDF can include a tax number when your community is configured to show one.
- Customers remain responsible for VAT and local tax invoicing outside Bevy when their jurisdiction requires it.
Card security (SCA)
Bevy Pay checkout is designed for Strong Customer Authentication (SCA) using 3-D Secure 2.0. The cardholder’s bank may require an extra verification step for online purchases, depending on local regulations and the bank’s risk rules.
Connect Bevy Pay
After Bevy Pay is enabled for your community (ask your Customer Success Manager or Bevy Support if paid ticketing is unavailable), connect Stripe from Admin and/or chapter Payments settings.
HQ admin (community payouts)
- In the Admin Dashboard, open Settings → Payments.
- Enter the bank account details for the community’s connected account.
- Select Save Account.
For whether organizers can choose paid ticket modes at all, see What HQ must enable first and Configure event ticketing.
Chapter payment lead (chapter-level payouts)
- Sign in as the chapter payment lead.
- Open the Chapter Dashboard → Settings → Payments.
- Complete Stripe onboarding (for example Start Selling) and return to Bevy when Stripe finishes.
Full chapter payment-lead setup, Payment Dashboard access, and lead changes: Chapter-level payouts.
How a paid ticket purchase moves money
- Organizers or HQ set ticket prices on a paid Bevy Ticketing event.
- Attendees pay by credit card at checkout.
- The purchaser pays the ticket price plus processing fees. Typical fees include:
- Stripe card processing in the United States: 2.9% + $0.30 per successful charge (international cards often add about 1%).
- Bevy processing fee: typically 1% of the presentment total (community configuration can vary — confirm with your Customer Success Manager).
- Funds settle to the connected Stripe account for the community (HQ) or chapter payment lead.
- Stripe payouts move available balance to the linked U.S. bank account on Stripe’s schedule (often a rolling multi-business-day deposit). Stripe may also charge payout or account fees on its side.
Tip: HQ vs chapter who controls pausing payouts, minimum balances, and disputes is covered in Managing paid events: payouts, refunds, and deleting attendees. Chapter payment leads manage many of those controls in Stripe’s Payment Dashboard from chapter Payments settings.
Refunds
From the event Registrations tab, use Refund total order for a full Bevy Pay order when refunds are enabled and you have permission. Partial refunds are not available in Bevy. Refunds must be within 180 days of the ticket purchase date and need enough Stripe balance.
Full steps, HQ enablement, low-balance Stripe-first path, and chapter-level carve-outs: Refund a paid ticket. For refund vs delete and payout-structure differences: Managing paid events: payouts, refunds, and deleting attendees. Registrations list overview: Manage event registrations.
Important: When a paid order is refunded, Bevy’s fee is typically returned to the community, but Stripe’s card-processing fees are not. There is no separate Bevy fee for the refund action itself. Chargebacks and disputes follow your payout model (HQ report / Support, or Stripe Dashboard for chapter-level payouts) — see the managing paid events article.
Checkout payment errors
| Message the purchaser sees | What it usually means |
|---|---|
| There was a problem processing your payment method. Please choose a different one and try again. | Hard decline from the card issuer. The purchaser should contact their bank and use a different card. |
| There was a problem processing your payment method. Please double-check your payment information and try again. | Soft decline. The purchaser can retry with corrected details; if it keeps failing, they should contact their bank (travel blocks are common). |
| There was a problem processing your payment method. Please review your information carefully before trying again. If the problem persists please contact our support. | Unrecognized decline. Retry once; if it continues, contact Bevy Support with the order details. |
Payouts paused for missing regulatory details
If ticket purchases succeed but organizers report that payouts are paused, the connected Stripe account may be missing required regulatory information.
- Open Payments settings in the Admin Dashboard (or chapter Payments for chapter-level payouts).
- Select the prompt to review or complete regulatory details (wording may vary).
- Finish every required field Stripe requests, then confirm payouts resume.
If the prompt is missing or payouts stay paused after you complete the form, contact Bevy Support or your Customer Success Manager.