Tenant isolation
Merchant credentials operate only inside their merchant scope. Customer sessions can access only records connected to the verified customer.
Security
Security boundaries built into the commerce model.
Customer identity, merchant authorization, pricing, sensitive credentials, and event delivery are designed around server-side controls rather than frontend assumptions.
Row Level Security
Customer-sensitive and merchant-sensitive data is protected with database authorization controls, with privileged mutations kept behind trusted backend paths.
Server-authoritative pricing
Financial amounts are resolved on the server and frozen into the checkout record rather than accepted from browser-submitted totals.
Signed webhooks
Outbound merchant events use event identifiers, timestamps, signatures, delivery logs, and retry-aware processing.
Secrets stay server-side
Provider secrets, service credentials, secret API keys, full card numbers, and CVV values do not belong in frontend bundles or application logs.
Retry-safe state changes
Checkout completion, payment confirmation, provider events, and downstream delivery are designed to tolerate duplicate or repeated attempts.
Authorization boundary
Merchant identity comes from authenticated context.
A request is not authorized simply because it contains a merchant identifier. Merchant APIs resolve tenant identity from a credential or trusted server-side registration and constrain the request to that scope.
Read about customer and merchant boundariesMerchant backend
Scoped server credentialMemberConsole API
Authorization policyMerchant-only records
Report a security concern
Send responsible security reports to security@memberconsole.com with safe reproduction details and no unnecessary customer or payment data.