A database per customer
Your operational data lives in its own database with its own database user — isolation is structural, not just a column filter. Nobody’s query can wander into your books.
Security
Built like money software — because it is
Tenant isolation, access control, and audit trails we can stand behind. Questions? Talk to us anytime.
How we protect the product
Structural controls — not optional settings
PayBlah reads receivables and talks to your customers. The protections below are how we earn that trust without overclaiming.
Secrets stay sealed
API keys are stored hashed. Tenant database passwords, OAuth tokens and webhook secrets are sealed at rest — readable by the system, not by people.
Sign-in, hardened
Password hashing, CSRF protection on browser forms, and optional TOTP two-factor with recovery codes — for customer accounts and platform admins alike.
Portal links that can’t be guessed
Debtor portal links are high-entropy bearer tokens with rate limiting, and failure responses are designed so tokens can’t be enumerated by probing.
API & webhooks, scoped and signed
Bearer-key API with no session-cookie auth, scoped keys, rate limits — and outbound webhooks signed with timestamp windows, so you can verify every event is fresh and genuinely from us.
Support access, on the record
Platform support sessions are reason-gated, time-boxed and audited — and they fail closed until dual-control requirements are met. Nobody browses your account casually.
Accounts & roles
Two roles, one audit trail, zero mystery
Admins change settings; Standard users work the queue. Every message sent and every user action lands in an append-only timeline per invoice — your evidence trail if anyone ever disputes what was said. Owner accounts can’t be deleted or demoted, and users are archived, never erased.
- Optional TOTP two-factor with recovery codes
- Append-only audit trail on every plan — never gated
- Deliberate, logged ownership transfer
The principles behind it
Three lines we never cross
Security is also about what the product refuses to do — on any plan, for any customer.
We never hold your money
Payment links go through an established payment provider, straight to you. PayBlah reads the result but never touches the funds — and card details are never seen by us, or by you.
Your data stays yours
Export everything, any time. Deletion requests are honored, and your customers’ data is processed under the data processing addendum — never marketed to, never resold.
The API can’t skip the rules
Everything the API can do obeys the same safety rails as the buttons on screen — pauses, approvals, opt-outs, audit. Automation is never a side door.
Responsible disclosure
If you believe you’ve found a vulnerability, email security@payblah.com with steps to reproduce. Please give us reasonable time to investigate before public disclosure — we read every report.
Related reading: Privacy Data Request · GDPR & Data Protection · Data Processing Addendum · Sub-Processors
Trust
Access control you can explain
We describe controls we actually run — tenant isolation, role-based access, audit trails — without inventing certifications we have not earned. Questions welcome anytime.
Contact us Sub-ProcessorsTrust is the product.
Bring your books — and your customers — somewhere built to treat both with care.