Security FAQ
Quick answers to the questions that typically come up in a security or IT questionnaire, with links to the fuller explanation. A few items are marked for confirmation with your Kaptio account team rather than answered here — this page describes the platform's technical design, not commercial or legal terms.
Hosting and infrastructure
Where is Edge hosted?
On Google Cloud Platform, in the EU (europe-west1 region), running on Kubernetes. See Platform architecture.
Are production and non-production environments separated? Yes. Production and staging are fully separate deployments with their own infrastructure; your production org and any sandbox org are registered against the environment appropriate to each. See How your Salesforce org connects.
Where does our data reside? Platform infrastructure is EU-based. Your Salesforce org's own data residency is governed by your Salesforce contract. See Data handling: data residency.
Tenant isolation
How is our tenant isolated from other Kaptio customers? Tenant context is established before any configuration is loaded or org data is queried — via your registered Salesforce org ID for org-initiated flows, via signed links for guest viewer and payment pages, and via per-tenant API credentials for webform intake. Configuration, signing secrets, and gateway credentials are all scoped per tenant. See Security model: tenant isolation.
Authentication and access control
How are sessions authenticated? User-triggered actions from Salesforce carry a signed, tenant-scoped token; platform access to your org uses OAuth 2.0. See Security model: authentication.
How do guests access documents and payment pages without a login? Through signed, time-limited links rather than a login — see Security model: public document and payment page access.
How are secrets and credentials stored? In an encrypted secret store, referenced from configuration by key — never as plain text in configuration files. See Security model: secrets and credential management.
Encryption
Is data encrypted in transit and at rest? Yes — TLS in transit for all traffic, and encryption at rest for stored credentials and OAuth connections. See Security model: encryption.
Payments
What is the difference between Edge Pay and Kaptio Pay?
Edge Pay is the guest- and agent-facing payment experience — the branded payment pages, links, and eligibility rules you configure via payment.yaml. Kaptio Pay is the payment processing service behind it, operated by Kaptio, which holds the gateway integrations and handles card data. Every Edge Pay payment is processed by Kaptio Pay; you never integrate with Kaptio Pay directly. See How Edge Pay relates to Kaptio Pay.
Does Edge or Kaptio ever see or store card numbers? No. Card data is captured directly in gateway-hosted fields and never reaches Edge's application servers, your Salesforce org, or your configuration. See Payment security.
What is the PCI DSS scope for a tenant using Edge Pay? Because card data never touches your systems or Edge's servers, your PCI scope is minimized; the payment gateway (Braintree, a PCI DSS Level 1 certified provider) carries the compliance burden for card data handling. See Payment security: responsibility matrix.
Is Strong Customer Authentication (3D Secure) supported? Yes, configurable per currency, with GBP and EUR enabled by default in the reference configuration. See Brands, currencies & 3DS.
Change control and auditability
How are configuration changes reviewed and tracked? Every change goes through a merge request, automated validation, and a review gate, giving a full audit history in your configuration's version control. See Security model: change control.
Items to confirm with your Kaptio account team
The following are commercial, legal, or operational details that vary by contract and are not published on this technical documentation site. Ask your Kaptio account team for current, tenant-specific answers:
- Formal compliance certifications (for example, SOC 2, ISO 27001) and their current status
- Data processing agreements (DPA) and subprocessor lists
- Formal data retention and deletion policy for your tenant
- Incident response and security patching cadence
- Backup and disaster recovery commitments (RPO/RTO)
- Penetration testing and vulnerability disclosure process