Let the people who can’t pay,
still check out.
GuardianPay is a drop-in payment-approval layer for apps and platforms whose users — kids, students, dependents — have the intent to buy, but need a parent or guardian to pay.
Built & validated inside Tutopiya · now opening to other teams
The buyer and the payer aren’t the same person
A huge share of users want what you offer but can’t complete a purchase alone. Today that gap quietly kills conversions and creates risk.
Carts that never close
A motivated student hits checkout, realises they need a parent, and the moment — and the sale — is gone.
Shared-card workarounds
Kids typing in a parent’s card is insecure, breaks trust, and drives chargebacks and disputes.
Consent & compliance risk
Taking money from minors without genuine guardian consent is a legal and reputational minefield.
One approval flow, three simple steps
GuardianPay sits beside your existing checkout. The user keeps the experience; the guardian keeps control.
The user requests
At checkout, a user who can’t pay taps “Ask a parent.” They choose what they want — no card needed.
The guardian approves
The linked parent or guardian gets a clear request and approves or declines in one tap, paying with their own method.
The purchase completes
On approval, payment clears and your product unlocks instantly — with a clean record of consent.
Built for any team serving non-paying users
If your users hold the intent but not the means to pay, this is for you.
We already solved this for ourselves
Tutopiya serves learners who rarely hold the purse strings. So we built a parent-approval payment flow, tested it with real families, and watched conversions climb. Now we’re opening it to other organisations wrestling with the same problem — and we want to talk to the teams who need it most.
Proven with real learners and guardians inside Tutopiya
Designed to sit beside the checkout you already run
Genuine guardian approval recorded on every purchase
Want this for your users?
We’re onboarding a small group of early-access partners. Tell us about your use case and we’ll be in touch — you’ll help shape what GuardianPay becomes.
- ✓ Early access ahead of public launch
- ✓ Direct line to the team building it
- ✓ No commitment — just a conversation
Request early access
Tell us a little about your organisation and we'll get in touch. No commitment — we're talking to teams who serve users that can't pay for themselves.
We'll only use your details to talk to you about GuardianPay. See our privacy policy.
Frequently asked questions
What exactly is GuardianPay? +
GuardianPay is a payment-approval layer you add to your existing checkout. When a user who can’t pay for themselves — a child, student, or dependent — wants to buy, they trigger a request that goes to a linked parent or guardian for one-tap approval. The payment only completes once it’s approved.
Who is this for? +
Any organisation whose users hold the intent to purchase but not the means or permission to pay: edtech and learning apps, kids’ and teen apps, gaming, subscriptions, marketplaces, and schools collecting fees.
How is this different from just asking for a parent’s card? +
Asking the child to type in a parent’s card details is clunky, insecure, and frequently abandoned. With a dedicated approval flow the guardian stays in control: they get a clear request, approve or decline it themselves, and pay with their own saved method — no card-sharing, fewer chargebacks, and a far higher conversion rate.
Is it built and working? +
We built and validated this approach inside Tutopiya for our own learners. It works. We’re now opening it to other organisations facing the same problem — and this page is how we’re gauging who wants it first.
How do I get involved? +
Request early access using the form on this page. We’re onboarding a small group of design partners and will reach out to understand your use case.
Solve the “I can’t pay for this” problem
Join the organisations getting early access to GuardianPay.
Request early access