The post-checkout page
The first thing they see, before any account exists in their mind. After paying, they’re redirected straight to a page showing:- What they bought
- Every benefit it granted — the license key in full, working download buttons, a GitHub invitation to claim
- An option to sign in and see the rest of their orders
This page only exists if you’ve set the post-checkout
redirect at your gateway.
Without it, the customer’s first experience is your gateway’s own thank-you page, and they have
to find their way to your store themselves.
Signing in
Athttps://yourstore.keyplar.com/login, showing your store name and logo.
They enter their email and continue. If they’ve set a password they’re asked for it, with a
one-time email link as the alternative. If they haven’t, a magic link is sent automatically.
Google and GitHub appear if you’ve enabled them.
Whichever they use, the account they land in is the one their orders are already attached to —
matched on the email address.
Inside the portal
Everything is scoped to what they’ve actually bought. A refunded order’s downloads stop working;
a cancelled subscription’s benefits disappear.
What they can do without you
The point of the portal is that most support requests answer themselves:- Re-download a file after losing it
- Find a license key they’ve misplaced
- Free an activation after reinstalling their machine
- Cancel a subscription
- Claim a GitHub invitation
- Export their data or delete their account
What still needs you
- Getting in when sign-in email fails → account access link
- Reaching one order when they can’t sign in at all → signed order link
- Replacing a leaked key → regenerate, where the gateway allows it
- Refunds → always at your gateway