Loading
One moment.
One moment.
Last updated: May 21, 2026
When Stripe confirms your payment, HelmXP runs a provisioning sequence automatically. This page explains each step and the expected timing.
The entire sequence runs in under 30 seconds.
HelmXP receives a signed webhook from Stripe confirming checkout.session.completed. The webhook signature is verified before any action is taken. If verification fails, the webhook is rejected and Stripe retries automatically.
HelmXP creates your Hub record with a unique identifier, your credit union's legal name, and your chosen plan. A subdomain is reserved: {hub-slug}.helmxp.com.
If your credit union name is already in use as a subdomain, HelmXP appends a short disambiguating suffix and notifies you by email so you can request a change.
Eight default Seat records are created:
The CEO Seat is the only Seat assigned at provisioning. All other Seats remain unassigned until you invite each executive by email.
A welcome email is sent to your CEO address with:
If the magic link expires before you use it, go to helmxp.com/login and request a new one.
Clicking the magic link signs you into your Hub and lands you on the Wheel — the main screen showing all eight Seat positions and their status. An onboarding checklist overlays the Wheel on first sign-in.
The following require action from you after provisioning:
If something fails during provisioning (rare — the sequence is idempotent and Stripe retries failed webhooks for up to 72 hours), you will receive an email from support@helmxp.com with instructions.
If your card was charged but you have not received a welcome email after 10 minutes, contact support@helmxp.com with your credit union name and the email address you used at checkout.
Your Hub's data is isolated from all other Hubs from the moment provisioning completes. See [[how-your-hubs-data-is-isolated]] for technical details.