No custody
We never hold funds. Crypto goes to the merchant wallet, not ours.
Checkout API
Customers pay fiat. Crypto lands in your wallet.
Sessions API. HMAC webhooks. Wallet locked from merchant settings. Buyers pay fiat through an on-ramp partner (mock today). Crypto goes straight to your own wallet. Card numbers never touch Railpointpay, and Railpointpay never holds your crypto.
Guardrails.
Path A. Merchant wallet only.
No PAN
Buyers pay through an on-ramp partner. Card numbers never hit railpointpay.com.
Signed webhooks
Processing then completed events for your backend. Payloads are HMAC-signed.
Wallet locked
Address comes from merchant settings. Buyer cannot change it at checkout.
Mock ramp
Sandbox mock for review today. Transak partner application in progress.
Your wallet
Fiat in on the ramp. Crypto out to your wallet. Path A. No operator custody.
Three steps.
Session to settlement on the merchant wallet. Once enabled, buyer KYC and payment processing are handled by the on-ramp partner (mock today). You stay responsible for your own business compliance (tax, consumer law).
Create session
Call the API with amount and currency. Wallet is stamped from merchant settings.
Buyer pays
On-ramp partner. Mock for review today. We never collect card numbers.
Delivered to your wallet (by the ramp)
Crypto to the merchant wallet. HMAC webhooks for processing, then completed.