The Boundary: Banking Core vs. Support Gateway
Financial institutions, neobanks, and fintech platforms operate on hardened core banking engines, fraud detection systems, and ledger databases. Exposing these core systems to external cloud SaaS helpdesks introduces severe compliance risks (SOC 2, ISO 27001, GLBA, DORA, and regional banking secrecy regulations).
Salamandr provides a secure, self-hosted support gateway that bridges customer communication with internal banking context without compromising security perimeters.
Custom Financial Context in the Ticket Sidebar
When a member reports a card transaction dispute or authentication failure:
- On-Demand Account Metadata: The agent sidebar queries internal microservices on the fly using sandboxed WebAssembly extensions, rendering member KYC verification tier, account standing, card status (Active, Frozen), and recent transaction identifiers.
- Zero Ledger Replication: Account data is never ingested, cached, or replicated into the helpdesk database. The context rail acts as a real-time viewfinder into internal systems.
- Direct Card Actions without PCI Scope: Secure action endpoints allow authorized staff to trigger card lock/unlock requests or issue transaction dispute receipts directly against internal payment switches.
Direct Messaging Channels with Private Keys
Financial customers increasingly rely on WhatsApp and messaging channels for prompt support.
- Bring Your Own App (BYOA): All Meta channels (WhatsApp Business API, Instagram, Messenger) authenticate directly using your organization’s verified developer credentials.
- No Intermediary Cloud Broker: Customer conversations flow directly from the Meta API into your self-hosted backend, eliminating third-party SaaS vendors sitting in the middle of financial discussions.
Ready to deploy on your own servers?
One command via Docker Compose. Free forever up to 5 agents.