The problem
A theatre’s guide can say a seat is step-free, while a notice for today’s performance says the lift is out. A guest who needs that route or a companion seat should know what the venue can confirm before committing to the ticket charge. Battersea Arts Centre published a performance-specific lift notice. Access Culture 2025 found that 71% of disabled visitors surveyed struggled to find clear accessibility information.
Before and after
| Before IfPay | With IfPay |
|---|---|
| A permanent guide may give an answer that no longer applies to this performance. | IfPay shows the original guide beside the dated notice and highlights the conflict for staff. |
| Guests have to piece together the way in and where their companion can sit. | The guest asks for either or both details and sees the venue’s answer on one pass. |
| Guests may commit to a charge before the access question is resolved. | An optional sandbox hold is voided when the venue reports an unverified detail. If every detail is confirmed, the guest chooses whether to approve payment. |
Try IfPay
Start with the lift-outage scenario. Keep both access details selected and choose Request access check. On your pass, Place test hold and Open venue workspace. The AI draft shows both source quotes, including the performance-day notice. Mark the route Could not verify, confirm the companion seat, add a short note for each decision, and Share venue decision. The guest pass shows Hold voided.
Try Verify both details in a new booking. Place a hold, record both confirmations as the venue, and return to the guest pass to approve the payment. Venue opens the AG Grid queue. Search, filter, sort, or reopen the requests you just created. Judges can open the hosted link directly, or install IfPay to a phone’s Home Screen.
How the technology fits
- AI evidence. IfPay Venue Notes v1 is a local, trained text classifier. It finds candidate access details, quotes the original notes, and keeps conflicting evidence open for staff review. The venue’s decision is separate from the model’s draft.
- PayPal Braintree Sandbox. GraphQL authorizes, submits, and voids the fixed $38 test amount. Capture requires every requested venue confirmation and a separate guest approval.
- AG Grid Community. The venue’s request queue shows actual access and payment states for the current sandbox workspace. Staff can filter to requests needing attention and reopen a case to see its evidence and decision.
Verified outcomes
We exercised both branches in the hosted app. The conflicting lift notice led to a $38 authorization being Voided. Confirming both details and approving payment returned Submitted for settlement. The automated suite passed 39 tests.
What’s next
The current build uses a fictional theatre and Braintree Sandbox. A venue pilot would connect verified staff accounts and real seat inventory, then measure how often guests get an answer before paying.
Built With
- ag-grid
- braintree
- javascript
- machine-learning
- node.js
- progressive-web-app
- vercel