Where Is Teller Hosted, and How Reliable Is It?
Teller runs on AWS (Oregon primary, Virginia DR) with a 99.9% business-hours SLA, annual SOC 2 Type 2, and 5-minute RPO.
No results.
Teller Government Cashiering uses a semi-integrated payment architecture that keeps your agency out of PCI scope while maintaining full control over your cashiering operations. Card data never touches your network — it goes directly from the payment terminal to the processor, while Teller handles everything else.
Here's how it works:
This approach gives you the best of both worlds: seamless cashier experience with minimal PCI burden.
Reduced PCI scope — Because card data never enters your systems, your Self-Assessment Questionnaire (SAQ) is significantly simpler. Most Teller clients qualify for SAQ B-IP or SAQ P2PE rather than the more complex SAQ D.
No card data storage — Teller stores transaction records, receipt numbers, and authorization codes — but never card numbers. There's nothing to encrypt because there's nothing sensitive on your network.
Processor flexibility — Teller integrates with major government payment processors. Your existing processor relationships can typically continue.
Teller supports modern payment standards:
Counter devices are certified to current PCI PTS standards.
Payment security is one layer of Teller's security posture:
Do we need to change processors?
Usually not. Teller integrates with most major government payment processors. We'll confirm compatibility during implementation planning.
What about phone payments?
For card-not-present transactions, Teller can integrate with virtual terminal solutions that maintain PCI compliance for MOTO (mail order/telephone order) payments.
How do we prove compliance to auditors?
Teller provides documentation of our security architecture, and our SOC 2 report is available under NDA. Your processor provides the PCI attestation for card handling.
Ready to discuss payment security for your agency? Contact us for a technical conversation about your compliance requirements.