Payment infrastructure
GRYPHEM PAY gives merchants a hosted checkout, a documented API and a payment timeline built from verifiable chain events. Payments run through our Bitcart account and are held for you until you withdraw them. Live payments open after verification and approval.
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 and a currency with your live key. Idempotency keys make retries safe.
POST /v1/payment-intentsThe customer lands on a hosted page with the exact amount and an address issued for this payment by our Bitcart account.
GET /c/{checkout_session}GRYPHEM re-checks every Bitcart update and marks the payment confirmed only when the invoice is complete.
detected → confirming → confirmedYour endpoint gets an HMAC-signed webhook with an event id you can deduplicate, and the amount is credited to your balance.
Gryphem-Signature: t=…,v1=…03 — Checkout
The hosted checkout is fast, uses no WebGL and never guesses. This is what your customers see once live payments are open.
In the asset the customer picks, taken from the invoice GRYPHEM PAY opens in its Bitcart account for this payment.
The address issued for this payment, with a QR code and a link that opens the customer’s wallet.
Detected, confirming and confirmed — each with a label, an icon and a plain-language reason.
A payment counts as confirmed only when Bitcart reports its invoice complete. Partial and late payments go to review.
Live payments open after verification and approval. Until then, no payment can be made through GRYPHEM PAY.
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_01JEXAMPLE00000000000000",
"store_id": "store_01JEXAMPLE0000000000000",
"environment": "live",
"object": { "type": "payment_intent", "id": "pi_01JEXAMPLE00000000000000" },
"data": {
"status": "confirmed",
"previous_status": "confirming",
"status_reason": "bitcart_complete",
"amount": "59.90",
"currency": "EUR",
"merchant_order_id": "order-123",
"fulfillable": true,
"quote": null,
"totals": null
}
}Get ready for live payments
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.
Submit business verification. GRYPHEM reviews it manually and enables live payments for your organisation after approval.
Call the API with your live 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.
Create your account and submit business verification now. Live payments are custodial and open only after approval — custody authorisation included. Nothing arrives by surprise.
