Overview
What BramaPay does, who it is for, and the contract an integration relies on.
BramaPay is for online stores, SaaS products, marketplaces, and other services that need server-controlled stablecoin checkout while receiving funds directly in a merchant-owned wallet.
What BramaPay handles
- project-scoped integration credentials;
- hosted payment instructions and status polling;
- exact-amount invoice attribution on a reusable wallet;
- blockchain detection and confirmation;
- platform-fee accounting;
- HMAC-signed webhook delivery with durable retries.
What remains under merchant control
- wallet keys and the payment funds;
- order state and fulfillment;
- refunds;
- API-key and webhook-secret storage;
- deduplication of fulfillment events.
Each project isolates wallets, API keys, invoices, webhook endpoints, and return URLs. A secret key selects its project automatically, so /v1/invoices rejects projectId, walletId, and return-URL overrides.
Non-custodial does not mean trustless fulfillment
BramaPay never needs the private key of a merchant payment wallet. Your backend must still authenticate BramaPay's payment signal before fulfilling an order.