Security at Eonebill
How Eonebill protects connected financial data, payment handoffs, account access, and sensitive documents.
Last implementation review: September 17, 2026
Encrypted bank tokens
Plaid access tokens are encrypted before database storage.
Provider-hosted checkout
Stripe and PayPal collect payer details in their payment flows.
Verified account access
Email verification, supported OAuth, and secure production cookies protect sessions.
Current controls
What the product does today
Each statement below is limited to a control visible in the current application implementation. Workflow-specific protection is identified as such.
Data protection
Encryption is applied to named sensitive workflows
Production responses instruct browsers to keep using HTTPS, while selected high-risk records receive application-layer encryption before storage.
- Plaid access tokens are encrypted with AES-256-GCM before they are written to the database.
- Vendor tax data, W-9 files, and completed e-signature PDFs use scoped application-layer encryption.
- These controls are described by workflow; Eonebill does not describe every stored field as application-layer encrypted.
Bank connections
Plaid handles bank sign-in; Eonebill stores an encrypted token
The connected-bank workflow loads Plaid Link for institution sign-in, then exchanges its temporary public token on the server.
- Eonebill’s server receives the temporary public token returned by Plaid Link, not bank sign-in fields from an Eonebill form.
- The resulting Plaid access token is encrypted before storage and is never returned to the browser.
- The connection is configured for transaction data; Eonebill does not request Plaid payment-initiation access.
Payments
Payment details stay in Stripe or PayPal checkout
Invoice and subscription payment flows send payers to provider-hosted checkout or approval pages instead of collecting card details in Eonebill forms.
- Stripe Checkout, Stripe Payment Links, and Stripe Connect Account Links provide the hosted payment and onboarding surfaces.
- PayPal invoice payments use PayPal order approval and capture APIs.
- Eonebill stores provider account, order, capture, and payment-status references needed to reconcile an invoice—not full card numbers.
Authentication
Verified accounts and restricted production sessions
Account access is managed through Better Auth with verified email/password accounts and supported social sign-in providers.
- Email/password registration requires email verification before account use.
- Google sign-in is configured, and Apple sign-in is enabled when its production credentials are present.
- Production sessions use secure cookies, trusted-origin checks, and a seven-day session lifetime.
Protected documents
Sensitive files use scoped encryption and access checks
Document protections are applied according to the sensitivity and delivery path of each workflow.
- W-9 files are encrypted before object storage and decrypted only in the associated vendor workflow.
- Completed e-signature PDFs are encrypted with a per-document key whose stored form is separately wrapped.
- Bank-statement downloads require authenticated organization access and return private, no-store responses.
Privacy controls
Account deletion and privacy choices are available
Users can initiate account deletion from security settings, review Eonebill’s privacy practices, and manage non-essential cookies.
- Web and mobile account-deletion paths call the same Better Auth deletion capability.
- The Privacy Policy explains collected data, service providers, retention, and California privacy choices.
- The site exposes cookie preferences and a Do Not Sell My Personal Information link.
AP-readable invoice design
Invoices designed for accounts payable workflows
Eonebill invoices are designed to be read correctly by AP systems like Ramp, Bill.com, and QuickBooks.
Exported PDFs keep selectable text and place invoice dates, PO number, legal names, remit-to details, payment instructions, totals, Tax ID / EIN, and currency in a consistent AP processing block.
Independent sample result
In a synthetic before-and-after benchmark, two public OCR extractors improved from 4/8 to 8/8 checked fields; a third fixed-schema demo improved from 2/6 to 4/6.
Scope of the claim
This is an independently tested document-design target, not a certification or guarantee from Ramp, Bill.com, or QuickBooks.
Sample last checked September 17, 2026 using synthetic business and payment details.
Clear boundaries are part of trustworthy security
No online service can guarantee absolute security. Eonebill limits this page to implemented controls, names the workflows receiving application-layer encryption, and updates the review date when those controls change.
Found a security issue?
Send the affected URL, reproduction steps, and any relevant request identifiers. Do not include passwords, raw bank tokens, tax IDs, or full payment details.
Contact Eonebill