Direct wallet settlement
Customer payments go directly to your business wallet. Gateway does not hold balances or intermediate funds.
Security model
Verify the Solana payment before your app ships access
Gateway is built around one operating rule: your app should update access only after the payment data has been checked and the callback has been verified.
Payment verification
Gateway checks recipient, amount, fee, and Solana payment status before a checkout becomes confirmed.
Server-side credentials
Your app keeps its API key on its server. Customer checkout pages never need it. The merchant console is a developer tool: it holds a key only in the open tab's memory and should not be used on a shared machine.
Explicit Telegram routing
Customers add @solknife_sandbox_bot and provide a Telegram chat id before payment notifications are sent.
Signed callback delivery
Callbacks are signed with HMAC-SHA256 over a timestamp and the body using the callback secret. Your backend rejects forged events, callbacks older than 5 minutes, and repeated delivery ids.
Checkout privacy posture
Hosted checkout pages are not indexed. Private payment intent URLs are treated as transaction surfaces, not marketing pages.