Glossary
Capture-on-Approval
Capture-on-approval is a payment pattern used in application-gated event ticketing where the payment processor (typically Stripe) authorizes a card at the time the applicant submits but does not charge it until the host approves the application. The pattern uses Stripe's "manual capture" mode (or equivalent on other processors): the authorization holds funds for up to seven days; the host approves or declines within that window; capture executes the actual charge only on approval. Declined applications release the authorization automatically with no charge, no refund, and no Stripe fee.
How it works
Mechanically, capture-on-approval rests on the distinction between authorization and capture in card processing. An authorization verifies the card is valid and reserves funds; a capture is the actual debit. Most consumer payment flows authorize and capture in one step (called "automatic capture"). Manual capture splits them: authorize at submission, capture later. For event ticketing, this means: (1) applicant submits with card on file; the platform calls Stripe with capture_method=manual; (2) the host reviews; (3a) on approval, the platform calls capture, the card is charged, the ticket issues; (3b) on decline, the platform cancels the authorization, the funds release. The authorization typically lasts 7 days; if the host doesn't decide in that window, the authorization expires and must be re-collected.
Where it applies
Capture-on-approval is the canonical payment flow for any application-gated event with paid tickets. Founder breakfasts, masterminds, retreats with curated cohorts, exclusive networking dinners, and member-tier renewals all benefit. Without capture-on-approval, hosts face two bad options: charge at submission and refund declines (incurs Stripe fees on declined applicants, creates friction), or wait until approval and re-collect payment (loses applicants who don't respond to the second prompt). Capture-on-approval cleanly avoids both — applicants commit; hosts curate; only approved applicants are charged.
Platforms that ship this
Capture-on-approval is the default flow for application-gated events. No additional configuration needed.
Stripe (the underlying primitive)
Stripe supports manual capture natively via the capture_method=manual parameter on PaymentIntents. Most event platforms can implement capture-on-approval against Stripe directly.
Eventbrite, Luma, Partiful
These ticketing platforms typically charge at submission. Capture-on-approval is not their default flow.
Common questions
How long does the Stripe authorization hold for?
Standard Stripe authorizations hold for 7 days. After 7 days the authorization expires and the platform must either capture or re-collect payment. Most application-gated event flows assume hosts review within this window.
Are Stripe fees charged on declined applications?
No. Stripe charges processing fees only on captured (charged) transactions. An authorization that is cancelled (decline) incurs no fee. This is the core economic advantage over the charge-and-refund pattern.
What if an applicant's card is declined at the authorization step?
Most platforms ask the applicant to provide a different card. The application is typically not submitted until a valid authorization is in place — this filters out invalid cards before the host wastes review time.
Related terms
SocialLoop is the AI event management platform from A to Z — built for hosts running recurring ticketed events with affiliate / community-partner distribution.
Start hosting