Security and PCI DSS
How Ginger protects card data and access to your platform, and what stays in your own PCI DSS scope.
Ginger runs your platform as a PCI DSS Level 1 compliant service provider. Card data is stored in Ginger's vault, and the hosted payment page collects it, so your merchants and your team don't handle card numbers in the usual flows.
Card data
- Vault. Ginger stores card details in its vault and gives the merchant a token. Processors receive the card from the vault; your systems and the merchant's never need the card number.
- Hosted payment page. When merchants use the hosted payment page or payment links, the card details go straight to Ginger. This keeps the merchant's PCI DSS scope small.
- Own payment pages. A merchant, or you, collecting card details in an own page or app is in a larger PCI DSS scope: every system the card details pass through must be compliant. See Your own 3-D Secure.
- Attestation of Compliance. Ask your Ginger contact for Ginger's current PCI DSS Attestation of Compliance (AoC), for your own assessment.
Access to your platform
- Portals. Every user has their own login, which they can protect with multi-factor authentication. After repeated failed logins, the account is locked for a while. See Manage your team.
- APIs. Only over HTTPS, with TLS 1.2 or newer. Keep admin API keys in a secret store and give each key only the permissions it needs. A project can be limited to a list of IP addresses. See Authentication and API keys.
- Your domain. Ginger issues and renews the TLS certificates of your domain. Add a CAA record and DNSSEC for extra protection. See Delegate your domain.
Availability
Ginger deploys the platform several times a day, to every platform instance at once. Monitor your platform with the health check, and follow the changelog.