SafeGate v5.5 / Merchant Integration Request / Public Mock

Merchant Integration Request Mock

This page shows how a future merchant can request SafeGate integration without exposing secrets, receiving a real API key, or triggering a production onboarding claim.

Public boundary: This is a public mock. It does not submit data to a backend, does not create a real merchant account, does not issue API keys, does not expose backend secrets, and does not claim Pi Mainnet settlement proof.

1. Mock Integration Request

Merchant / Project Name Contact Email Requested Environment Expected Verification Volume Use Case

Mock Request Result

Click “Create Mock Request” to generate a public mock response.

2. Integration Request Boundary

No production merchant account is created.
No real API key is issued.
No backend secret, service role, wallet passphrase, or access token is exposed.
Future production access would require manual review, scoped keys, rate limits, and audit logging.
Requested scopes are future boundaries, not active production permissions.

3. Future Requested Scopes

[
  "receipt.verify",
  "receipt.read_trust_summary",
  "merchant.read_own_records",
  "merchant.export_evidence_summary"
]

4. Future Review Checklist

Merchant identity and contact review.
Use-case review for payment-triggered access.
Rate-limit profile selection.
API key lifecycle approval.
Webhook and receipt signing readiness.
No-secret-exposure confirmation.
Controlled pilot evidence review before production claims.