Card data never reaches our servers
Card data handled by a PCI DSS Level 1 processor — it never touches our servers. Card details are captured in the processor's hosted fields; Umbra receives a token, never a card number.
Security
You are routing client money through us.
The controls should reflect that. Here is what protects your data and your clients' payment details.
- Card handling
- PCI DSS Level 1 processor
- Encryption
- TLS 1.2+ / AES-256
- Access
- Owner and employee roles
- Traceability
- Activity history and audit report
Encrypted in transit and at rest
TLS 1.2+ in transit, encrypted at rest on AWS, with sensitive credentials held in AWS KMS.
Access scoped to the business
Owner and employee roles for each business, and nothing from another business on the platform.
Activity you can trace
Activity history on every invoice and payment, plus an audit-trail report.
Reported, not assumed
Reconciliation runs continuously against the processor and against QuickBooks. Divergence is surfaced in a queue rather than discovered at month end.
Found something? Write to support@umbrapay.com and we will respond directly.
Let us elevate your invoicing experience.
Reduce cost, remove the tedious parts, and get the insight you need to grow — without adding another tool to the stack.