Payment infrastructure · Sandbox preview
GRYPHEM PAY gives merchants a hosted checkout, a documented API and a payment timeline built from verifiable chain events — settling into wallets you control. Start in a sandbox that behaves like the real thing, without pretending to be it.
The 3D scene is taking longer than expected.
Showing still coins — 3D is unavailable on this device.01 — The moment of trust
A customer presses pay and value starts to move. Somewhere else, a merchant waits for certainty. Between them sits every question a payment raises — which network, which amount, how final. GRYPHEM PAY answers each one with evidence you can read, verify and keep.
Every state in GRYPHEM PAY carries its proof: the quote, the transaction, the block, the confirmations and the signed webhook.
02 — From request to receipt
Your server posts an amount, a currency and the networks you accept. Idempotency keys make retries safe.
POST /v1/payment-intentsThe customer lands on a hosted page with a locked quote, a unique address and the exact amount.
GET /c/{checkout_session}Watchers record each transfer; the finality engine waits for the confirmations you configured.
detected → confirming → confirmedYour endpoint gets an HMAC-signed webhook with an event id you can deduplicate.
Gryphem-Signature: t=…,v1=…03 — Try it
This panel talks to the GRYPHEM sandbox API. Pick a test network, lock a quote and simulate a transfer on our deterministic chain simulator. No wallet needed, and no real value moves.
Creates a real checkout session on the demo store, a clearly labelled sandbox fixture. Sessions expire after a short time.
Payment status
Simulated transfers are labelled “Simulated (simnet)”. Exchange rates in the sandbox are fixed test values, not market data.
04 — For developers
Scratch the card with the coin — or press “Reveal now” — to see what your server receives when a payment confirms.
Gryphem-Signature: t=1792411471,v1=5f0c…e41b
{
"event_id": "evt_01JEXAMPLE00000000000000",
"event_type": "payment.confirmed",
"api_version": "2026-10-01",
"created_at": "2026-10-20T12:04:31Z",
"merchant_id": "org_demo_001",
"store_id": "store_demo_001",
"environment": "test",
"object": { "type": "payment_intent", "id": "pi_01JEXAMPLE00000000000000" },
"data": {
"status": "confirmed",
"previous_status": "confirming",
"amount": "59.90",
"currency": "EUR",
"network_id": "bitcoin:testnet",
"asset_id": "btc-testnet",
"amount_received": "0.00099834",
"confirmations": { "current": 2, "required": 2 }
}
}Try the sandbox
Never paste a live key into a browser. This page will never ask for one.
05 — Integration
Sign up, verify your email and create an organisation and store in the dashboard.
Register a watch-only extended public key, or use a simulated wallet while you build. We never hold private keys.
Call the API with a test key. Every create request is idempotent and returns a checkout URL.
Redirect to the hosted checkout or share a payment link. States update in real time.
Check signatures against the raw body, deduplicate on event id and query the API before fulfilling.
Build against test networks and a deterministic simulator. When live payments become available, they will arrive behind explicit reviews — not by surprise.
