SafeGate v5.3 / Merchant Console / Public Mock

Merchant Verification Console Mock

This page shows how a merchant-facing SafeGate verification console could verify a receipt ID, return a trust summary, and fail safely for invalid, unknown, or ambiguous states.

Public boundary: This is an interactive public mock. It is not a production merchant console, not a production public API, does not expose API keys, does not expose backend secrets, and does not claim Pi Mainnet settlement proof.

1. Mock Console

Receipt ID

Sample receipt IDs:

Ibrahim Gonul Tugba Unal Turgay Invalid Not Found Ambiguous

Verification Result

Click “Verify Receipt” to run the public mock.

2. Merchant Trust Summary

A future merchant console should not only show whether a payment happened. It should show whether the post-payment trust path is complete: finalized payment, receipt proof, access unlock, and merchant-side record.

Payment Finalized

Was the payment state finalized in the controlled evidence flow?

Receipt Proof Created

Was a receipt proof generated after the payment finalized?

Access Unlocked

Was digital access unlocked only after verification?

Merchant Record Found

Does the merchant-side record exist for review and reconciliation?

3. Mock Data Set

[
  {
    "tester": "Ibrahim",
    "orderId": "TP-DEMO-273551",
    "receiptId": "SG-RCPT-1781465776152",
    "paymentState": "PAYMENT_FINALIZED",
    "accessState": "UNLOCKED",
    "merchantRecord": "FOUND"
  },
  {
    "tester": "Gonul",
    "orderId": "TP-DEMO-482507",
    "receiptId": "SG-RCPT-1781527252627",
    "paymentState": "PAYMENT_FINALIZED",
    "accessState": "UNLOCKED",
    "merchantRecord": "FOUND"
  },
  {
    "tester": "Tugba",
    "orderId": "TP-DEMO-519861",
    "receiptId": "SG-RCPT-1781533835531",
    "paymentState": "PAYMENT_FINALIZED",
    "accessState": "UNLOCKED",
    "merchantRecord": "FOUND"
  },
  {
    "tester": "Unal",
    "orderId": "TP-DEMO-480574",
    "receiptId": "SG-RCPT-1781542533448",
    "paymentState": "PAYMENT_FINALIZED",
    "accessState": "UNLOCKED",
    "merchantRecord": "FOUND"
  },
  {
    "tester": "Turgay",
    "orderId": "TP-DEMO-227028",
    "receiptId": "SG-RCPT-1781550995179",
    "paymentState": "PAYMENT_FINALIZED",
    "accessState": "UNLOCKED",
    "merchantRecord": "FOUND"
  }
]

4. Fail-Secure Console Behavior

Malformed receipt IDs return INVALID_RECEIPT_ID and do not unlock access.
Unknown receipt IDs return RECEIPT_NOT_FOUND without leaking internal records.
Ambiguous verification returns VERIFICATION_AMBIGUOUS and fails secure.
Future unauthorized merchant states should not disclose whether a receipt exists.
No stack trace, service role, access token, wallet passphrase, or backend secret is exposed.