FAQ
Straight answers.
If something here is unclear or missing, ask us — the answer will probably end up on this page.
The product
When can I accept real payments?
Once GRYPHEM approves your business verification and every platform release gate is approved — security, operational and legal reviews, including any authorisation required to hold customers’ crypto-assets. You can create an account and submit verification now.
Does GRYPHEM PAY hold my funds?
Yes, once live payments are enabled for your account: processing is custodial. Customers pay the platform’s wallets through GRYPHEM PAY’s Bitcart account, GRYPHEM PAY holds the funds on your behalf as a balance, and you withdraw them through payouts that, by default, a second member of your team approves and that a GRYPHEM operator always reviews. Until then, nothing is held for you.
Which networks and assets are supported?
The assets held by the platform’s Bitcart wallets. Each checkout lists the assets it offers with the exact amount and address, and signed-in merchants see the same list in the dashboard. Support is never inferred from a token symbol.
Which payment methods do you accept?
Crypto only. Customers pay from their own wallet in one of the assets offered at checkout. Card, PIX and bank transfers are not offered.
Payments
When should I ship an order?
When the payment is confirmed and you have verified the signed webhook. Detected payments are not final.
What happens if a customer pays too little or too late?
A partial payment moves to underpaid and appears in your review queue with the evidence. Funds that arrive after the invoice expired are held for review and credited only after an operator verifies them. Nothing is credited silently.
Can payments be reversed?
Crypto transfers have no chargebacks. Refunds are sent by you from your wallet, and recorded against the payment.
Who pays network fees?
The customer’s wallet pays the network fee when sending. Platform fees are invoiced to the merchant separately.
Developers
How do I prepare my integration before going live?
Follow the going-live checklist in the docs: verify signatures over the raw body, deduplicate on event ID, make every create request idempotent and handle every payment state. Once live payments are enabled for your organisation, send a test event to your endpoint from the dashboard before your first payment.
How are webhooks secured?
Each delivery is signed with HMAC-SHA256 over the timestamp and raw body using your endpoint secret, and carries a stable event ID for deduplication.
Is there an SDK?
Yes — a TypeScript SDK and a webhook verifier, with more languages documented in the developer docs as they become available.
Still unsure? Contact the team.