Pi.createPayment → Backend Verified Receipt
This page is the controlled SafeGate V9 Pi SDK Testnet payment flow. A frontend callback alone cannot create a receipt, evidence record or access unlock. Receipt and evidence state are requested only after the backend verifies the payment state.
Flow:
1) Health
2) Create durable invoice
3) Pi authenticate
4) Pi.createPayment
5) Backend approve
6) Backend complete
7) Backend verified state
8) Guarded receipt/evidence
9) Public verify
1) Health
2) Create durable invoice
3) Pi authenticate
4) Pi.createPayment
5) Backend approve
6) Backend complete
7) Backend verified state
8) Guarded receipt/evidence
9) Public verify
V9 Pi payment page loaded. Run Health, then Create Invoice, then Pi Authenticate.
Blocked claims: production ready, Mainnet payments live, official Pi partner, fully Pi SDK integrated. This is controlled pilot / Testnet-oriented readiness flow.