Security Architecture & Verified Safeguards
Trustworthy financial tools state only what their codebase actually enforces. Below is a strictly factual summary of how reconcilebankstatement handles uploads, access tokens, and PDF unlock passwords—plus infrastructure items clearly noted for deployment verification.
1. Implemented Application Security Controls
Zero Bank Login Credentials Collected
reconcilebankstatement never requests online banking usernames, passwords, MFA codes, or third-party bank-feed aggregator tokens. You retain full control by uploading exported statement files directly.
Server-Side API Key Isolation
In default proxy mode (/api/reconciliation/*), server-to-server requests attach authentication headers from server environment configuration without exposing secrets to client JavaScript.
Input & Route Validation
Reconciliation identifiers are validated against a strict pattern (^[a-zA-Z0-9_-]{3,128}$) before upstream requests; both client and API route upload handlers enforce file extension allowlists and the 100 MB limit prior to forwarding.
No-Store API Caching & Redirect Blocking
API proxy calls set cache: "no-store" and redirect: "error", and return Cache-Control: no-store headers on JSON responses so financial payloads are not cached by shared CDN edges.
2. Encrypted PDF Password Handling
When reconciling a password-protected PDF statement, optional bank_statement_password or business_ledger_password inputs use masked type="password" fields with autoComplete="off" and are forwarded directly in the multipart upload request for transient in-memory decryption. Passwords are not saved in browser sessionStorage, localStorage, or cookies.
3. Webhooks & Transport Security
Optional completion webhooks enforce https:// URL validation before submission and accept an optional webhook_secret for HMAC-SHA256 payload verification. All public traffic to https://reconcilebankstatement.online is served over HTTPS/TLS in production so uploads and reports are encrypted in transit.
4. Processing Boundaries & Vulnerability Reporting
While this web application enforces strict upload validation, non-persistent cache headers, and masked transient password handling, storage-at-rest and automated file purging are governed by the configured upstream reconciliation processor. To report a security concern, write directly to [email protected] or read our Privacy Policy and Data Retention Policy.
Related Documentation & Trust Resources
Ready to compare your bank statement against your ledger?
Upload PDF, image, CSV, or XLSX files directly in the workbench or test immediately with our sample CSV pair.