Skip to content

Engineering controls for payment operations

The items below reflect implemented backend and dashboard controls. They do not constitute PCI DSS, AML or licensing certification by themselves.

Do not present this page as a compliance certificate. Legal counsel and accredited assessors remain required for regulatory claims.

Secure API authentication

Merchant integrations authenticate with hashed API keys. Dashboard sessions use HttpOnly cookies. Email verification is required for every account.

Data protection practices

Cardholder data is kept out of this platform — payments rely on hosted checkout or provider tokens. Secrets are encrypted at rest; plaintext API secrets are shown once.

Fraud and monitoring signals

Risk assessments and transaction monitoring alerts support operational review. Decisions remain human-driven in the console.

Access control

Role-based permissions and merchant isolation constrain who can read or mutate tenant data.

Auditability

Append-only audit logs record actor, action, resource and metadata for administrative review.

Webhook integrity

Outbound webhooks are signed with HMAC. Provider inbound webhooks verify signatures before processing.

Ask about security reviews