Tickets for your home crowd.

The first pilot clubs are Dade County FC and EasyChamp FC. Sign in to the club’s Commerce workspace to check access. Other clubs can discuss joining the pilot with EasyChamp; creating a club does not automatically enable ticket sales.

The club’s assigned business owner opens Payments and chooses Connect Stripe. Use the Stripe account that should receive this club’s money. Stripe hosts the business verification and bank-account steps. Club staff can check status, but only the assigned owner can connect the receiving account. Do not send banking details to EasyChamp support.

In Payments, check the owner’s name, receiving Stripe business and account ending. Then return to Commerce and refresh its Ready for matchday? checklist. It must confirm readiness for the mode shown: Stripe payments and payouts ready for Live payments, or Stripe test checkout ready for Test mode · no real payments. A connected live account alone does not confirm readiness for test checkout. Resolve any incomplete setup or recovery notice, confirm pilot access and explicitly publish an offer. A test order never represents a real payment or bank payout.

No. USD $5 is the starting home-ticket default. A manager chooses a scheduled club event, marks it as a home game, sets capacity and explicitly publishes its ticket offer. Change the club default for future offers or set a different price for an individual event before orders exist. A fixture title is not used to guess whether a game is at home.

An offer’s price and event are fixed once orders exist, so existing buyers keep the terms they accepted. Use new event inventory for a different price. Capacity cannot be reduced below reserved or sold tickets. Pausing sales closes unpaid checkout links; confirmed orders remain in the club’s history.

A manager creates a percentage-off code in Commerce, from 1% to 100%, with an optional future expiry and maximum number of redemptions. Codes use 4–32 letters, digits or hyphens and are stored in uppercase. They apply to this club’s event-ticket product on its receiving Stripe account. Fans enter the code before opening Checkout; a code from another club or an expired or exhausted code cannot discount the order. These pilot codes do not change registration fees or existing registration installment schedules.

Yes, after Stripe confirms the zero-total checkout. The order becomes complimentary and receives a ticket for each place. An unconfirmed browser return, pending checkout or failed payment does not create valid tickets.

Yes. Fans can buy as guests from the club’s published ticket page and return from Stripe to a private order receipt. That page shows verified payment status and tickets after payment or complimentary checkout is confirmed. Use Copy private receipt link to keep access on another device, or return in the browser used to order. Anyone with that private link can view the order and its admission codes, so keep it private. Stripe’s own email receipts follow the club’s Stripe settings.

A club manager opens Commerce → Admission and chooses Scan with camera. Allow camera access, then point the phone’s rear camera at the fan’s ticket QR. A readable code is checked and admitted once, then the camera closes. If the camera is unavailable or access is denied, close it and paste the ticket code, or use a scanner that enters text. Choose Check and admit. Wait for the recorded result: repeated scans show already admitted, and void or foreign-club tickets do not admit anyone.

For Live payments, the payment belongs to the club owner’s connected Stripe account shown in Payments. Stripe’s fees, account requirements and payout schedule determine the bank payout. Test mode creates no real payment or bank payout. EasyChamp does not substitute a staff member’s or temporary custodian’s account. Review the receiving business and payment mode before publishing or sharing a ticket offer.

Managers can refund a full order through Commerce on the original receiving account. A refunded order keeps its receipt and history, and its tickets become void. A complimentary order is voided without a money refund. A partial refund recorded by Stripe also voids admission until the club resolves it; it does not leave every ticket usable.

The club is preserved for ownership recovery. New sales pause, unpaid checkout links are closed, and a verified new business owner must be assigned before selling resumes. Existing payments and refunds stay linked to their original receiving account. The temporary platform custodian never becomes the club’s payout recipient.

Yes, once the club has completed Stripe setup and published a ticket offer. Share that offer’s public link, or print a QR code pointing to it. Fans open the page on their own phones and complete hosted Stripe Checkout. Staff then scan the issued ticket in Commerce → Admission. The purchase QR opens checkout; the private ticket QR confirms admission. Scanning a ticket does not charge a card.

Stripe supports Tap to Pay on compatible iPhones and Android phones, but native Tap to Pay is not yet available inside EasyChamp Club. A browser redirect cannot turn the phone into a contactless card reader. Eligible merchants can use the separate Stripe Dashboard mobile app for in-person contactless payments. Those standalone charges do not create EasyChamp tickets or reserve event capacity; keep their gate records separate. Integrated Tap to Pay needs a further app release and device verification.

Yes. Link its ticket buttons to the club’s public EasyChamp ticket page, or to a specific published offer. Fans, staff and the app then use the same prices, capacity, promotion codes and order history. Publish and manage the offer in Commerce first. An independent Stripe Payment Link or Square checkout does not automatically create an EasyChamp admission ticket. Existing registration or shop payments can keep their own checkout while ticket sales use the shared offer.

This pilot introduces no new EasyChamp subscription or platform fee; Stripe’s processing fees still apply. A monthly Commerce add-on is planned for later, with pricing and a launch date still to be announced. Existing Club App plans are separate. Start the pilot in the web workspace. App download availability and in-app Commerce shortcuts are separate from this browser workflow.