A $150 festival ticket is a barrier to attendance for a lot of people. A $50 deposit and two $50 monthly payments is not. The total is identical. The barrier is not.
I built a flexible payment plan system for Convenely — the event/festival WordPress platform I have been developing — and the economics of it are interesting enough to write about.
The Problem with Ticket Pricing
Event organisers face a pricing dilemma. Set the price high enough to cover costs and you exclude lower-income attendees. Set it low and you undercharge for the experience you are delivering. Offer a discount for “early bird” buyers and you train your audience to wait.
Flexible payment plans resolve this without a discount. The total price stays the same. The buyer gets cash flow flexibility. The organiser gets committed attendees who have paid a deposit — financially, psychologically, and practically more committed than someone who clicked “add to cart” and has not paid anything yet.
For community events and festivals with a culturally diverse, mixed-income audience, this distinction matters.
How the Stripe Integration Works
The Flex-Pay system uses Stripe’s Payment Intents API, not Stripe Billing subscriptions. Here is why: subscriptions have a monthly-billing semantic that does not map cleanly to “pay for this specific ticket in three installments and then the payment obligation is done.” Payment Intents give more control over the charge schedule.
The data model:
- A
planrecord defines the installment schedule: number of payments, intervals, amounts (either equal splits or a custom schedule) - A
paymentrecord tracks each scheduled and completed charge against a plan - On checkout, the buyer pays the first installment immediately (Payment Intent, confirmed at checkout)
- A cron job runs daily, identifies payments due, and creates new Payment Intents via the Stripe API for each
The cron-based approach means the charge schedule is visible and auditable in the WordPress database before it happens — staff can see what is coming, adjust schedules in exceptional circumstances, and reconcile against Stripe’s dashboard.
Interac e-Transfer as a Canadian Option
Stripe’s card payment coverage in Canada is good but not universal. For attendees who prefer Interac e-Transfer — which is ubiquitous in Canada — I built an IMAP-based Interac polling system: the platform monitors a designated email inbox for Interac notification emails, parses the sender, amount, and reference, and matches the incoming transfer against open payment records.
This is not elegant engineering. It is the only option Interac provides to non-bank developers. It works reliably when the email notification format is consistent and when the buyer includes a reference in the message field.
For a Canadian festival audience, offering Interac alongside Stripe card payments meaningfully increases payment completion rates.
The Attendee Experience
The checkout flow for a flexible payment ticket:
- Buyer selects the ticket and chooses a payment plan (or pays in full)
- Checkout collects Stripe payment method (card) or Interac instructions
- First installment is charged immediately
- Buyer receives a confirmation email with the payment schedule
- Each subsequent installment triggers an automatic charge attempt and an email receipt
- Failed charges send a reminder and retry once; a second failure flags the ticket for staff review
The buyer’s account page shows their ticket, their payment history, and their upcoming installments. They do not need to do anything after the initial checkout — the platform handles the rest.
What This Changes for Organisers
Revenue is predictable. Rather than a spike of sales in the week before the event, payment plan purchases spread revenue across two to four months. Cash flow planning is more straightforward.
Committed attendees. A buyer who has paid a deposit is more likely to show up than one who has not. No-show rates for flexible payment ticket holders in the Convenely beta have been lower than for full-price purchases.
Reduced support burden. Automated charge handling means staff are not manually invoicing installment buyers. The platform handles the schedule, the retries, and the receipts.
The Technical Debt to Watch For
Failed payment handling is where complexity lives. What happens when the second installment fails? Does the ticket get revoked? Does the buyer get a grace period? Is there a manual review step? These are policy decisions, but they have to be encoded in the system.
Refund arithmetic is non-trivial. If a buyer cancels after two of three installments, what gets refunded? The answer depends on the organiser’s refund policy, and the system has to support multiple policies without manual arithmetic.
Stripe reconciliation. Every charge in Stripe needs to be reconcilable against a payment record in WordPress. An audit tool generates a CSV of expected vs. actual charges — a reconciliation step that catches any drift between the database and Stripe’s state.
Worth Building
For events where ticket price is a meaningful access barrier, flexible payment plans are worth the implementation complexity. The data model is not trivial, but it is manageable. The Stripe integration is standard. The operational benefit to both organisers and attendees is real and measurable.