Payment security
This page describes how Edge Pay handles card data, gateway credentials, and regulatory authentication requirements. For the functional payment flow, see Edge Pay overview; for the org-side setup, see Salesforce integration.
Card data never touches Edge or your Salesforce org
Card details are captured in payment-gateway-hosted form fields, not in any field owned by Edge or by your org. Edge renders the payment page and orchestrates the flow, but the card number, expiry, and CVV are submitted directly from the guest's browser to the gateway. Your configuration, your Salesforce org, and Edge's own database never receive or store raw card data — they receive only the payment result (approved/declined, a masked card summary, and a gateway reference).
This scope — no card data touching your systems or Edge's application servers — is what keeps PCI DSS scope minimal for both you and Kaptio; the gateway itself carries the PCI compliance burden for card data handling.
Gateway and processing
Card payments process through Braintree, reached via Kaptio's payment processing service. Braintree is a PCI DSS Level 1 certified payment service provider. The specific processing endpoints for your environment are provisioned and managed by Kaptio; you do not configure gateway endpoints directly.
3D Secure and Strong Customer Authentication
3D Secure (3DS) is applied per acquiring currency. The baseline configuration enables 3DS for GBP and EUR, reflecting Strong Customer Authentication (SCA) requirements for UK and EU acquiring; other currencies default to 3DS optional. See Brands, currencies & 3DS for how this is configured per tenant.
Gateway credentials
Gateway API keys and merchant credentials are never stored in your configuration as plain text. They are held in the platform's encrypted secret store and referenced from payment.yaml as vault:: keys; the configuration repository's validation pipeline rejects any literal credential. See Security model: secrets and credential management.
Call-center and phone (MOTO) payments
For agent-assisted payments taken over the phone, the platform supports card vaulting through the same gateway-hosted fields — the agent never types or sees the card number, and Edge does not process or store it directly. See Edge Pay: entry scenarios for the call_center scenario.
Responsibility matrix
| Area | Responsible party |
|---|---|
| Card data capture and storage | Braintree (gateway) |
| PCI DSS compliance for card data handling | Braintree, as the PCI DSS Level 1 certified processor |
| Gateway credential provisioning and rotation | Kaptio |
| Payment page hosting, session orchestration, eligibility rules | Kaptio (Edge platform) |
| Booking status, amounts, and payment schedules | Your Salesforce org, configured by your team |
| 3DS/SCA policy per currency | Configured jointly with Kaptio at onboarding, editable in payment.yaml |
Where to go next
- Security model — platform-wide authentication, encryption, and tenant isolation
- Edge Pay overview — the functional payment flow and capability model
- Security FAQ — compliance and certification questions