Verification-first UPI checkout
Payment integrity operations
Payments
Session queue
| Customer | Amount | Status | Score |
|---|---|---|---|
| Meera Shahmeera@example.com | ₹2,499.00 | UNDER VERIFICATION | 72% |
| Rahul Menonrahul@example.com | ₹899.00 | VERIFIED | 94% |
| Anika Raoanika@example.com | ₹1,299.00 | PENDING PAYMENT | 0% |
| Dev Kapoordev@example.com | ₹1,999.00 | COMPLETED | 98% |
| Isha Nairisha@example.com | ₹499.00 | CHECKOUT OPENED | 0% |
Verification
Review discipline
- UTR capturedValidated and sanitized before storage.
- Evidence checkedScreenshot type and signature checks are enforced.
- Integrity scoreServer computes confidence; client cannot mark paid.
- Append-only auditEvery state transition creates an immutable event.
Projects
API key scoped checkout
Project keys are modeled separately from payment sessions so every protected read or write can verify ownership before returning data.
Audit logs
Events over mutation
Historical payment events are append-only. Payment rows hold the current state, while event rows preserve what happened and when.