Registration
Optional assisted registration for eligible EventsPaid Registration
Connect eligible registration to Stripe payment. Distinguish submitted forms, pending payment and confirmed registration throughout the participant journey.
Interactive preview
See Paid Registration in action
Illustrative example with fictional data, not live customer records. Silent and local to this page.
Tickets
Illustration only. No payment is taken.
| Ticket | Sold | Cap |
|---|---|---|
| Day pass | 311 | 400 |
| Workshop add-on | 74 | 80 |
Paid registration: Ticket chosen
How organisers set it up
- 1
Agree the payment scope
Confirm eligibility, Stripe configuration and the intended registration charges. Do not confuse attendee registration payments with the organiser's StampRise Event package.
- 2
Configure the form and payment journey
Use the supported pricing and payment settings. Explain the amount, applicable conditions and what confirmation means.
- 3
Test more than success
Review the successful payment path as well as cancellation, failure and a returning pending registration. Payment must be confirmed through the supported service flow, not a browser message alone.
What participants experience
The participant submits the form and follows the required Stripe checkout step. They receive the registration state appropriate to the verified payment outcome. Closing a checkout window or returning to a page does not itself prove payment succeeded.
Settings and controls
Payment and confirmation
Only the appropriate confirmed state should lead to the advertised admission or Passport access. Unpaid registrations remain distinct.
Terms and corrections
Publish clear cancellation and refund terms and use the supported authorised process for corrections. Do not promise automatic refunds or access changes without checking the actual flow.
Illustrative guided walkthrough
See how Paid Registration could play out
Sample scenario for explanation only. This is not live product data, a screenshot, or a real registration or draw.
Scenario: An eligible Event requires payment before confirming a registration.
Reporting
Review registration and payment records together while preserving their separate meanings. A successful payment does not establish Event attendance or activity completion, and a refund record is not the same as an admission reversal.
Limitations and boundaries
- The supported registration payment provider is Stripe.
- Paid registration is not the same purchase as unlocking an organiser's Event package.
FAQ
Frequently asked questions
The supported registration payment integration uses Stripe.
No. The system must verify the payment outcome before treating the registration as paid.
No. Participant registration payments and the organiser's package purchase are separate.
Keep reading
Related features
Event Registration
Explore optional StampRise Event registration: forms, invitations, payments, admission, badges and Passport access, with assisted availability explained.
Read moreRegistration Forms
Prepare hosted or embedded registration forms with custom questions and explicit publication. Keep draft changes, participant consent and saved versions clear.
Read moreEvent Check-In & Admission
Use authorised registration QR scanning for Event admission, walk-ins and status review. Keep admission separate from session check-in and Passport stamps.
Read moreRegistration-to-Passport Access
Link eligible registration to a Passport on confirmation, admission or staff approval. Preserve explicit continuation, identity checks and activity rules.
Read moreTalk to us about Paid Registration
This capability is set up with the StampRise team for eligible events.