Payment Card Industry Data Security Standard (PCI-DSS) provides a framework developing a robust security process for credit card transactions. Any merchant or service merchant provider accepting, transmitting, and/or storing cardholder data must be PCI compliant.
Recurly is PCI-DSS Level 1 compliant as a service merchant provider. Security is a top priority for Recurly. To that end, we meet and exceed all industry-standard payment security practices to protect you and your customers.
PCI Compliance for Merchants
As a merchant using Recurly, your level of PCI compliance is determined by one simple test: does your customers’ sensitive cardholder data (credit card number, security code) pass through your environment? If you use our hosted payment pages or transparent post to submit cardholder data, the answer is no.
Hosted Payment Pages
Using our hosted payment pages is the easiest way to start accepting subscription and reduce your PCI compliance scope. When you use Recurly’s hosted payment pages, your customers’ sensitive cardholder data is sent directly to Recurly. Their cardholder data never passes through your environment. As a merchant, this qualifies you for the simplest PCI compliance level.
Merchants using Recurly’s hosted payment pages qualify for the shortened PCI DSS Self-Assessment Questionnaire A.
Merchants using Recurly.js are eligible to complete the shortened PCI DSS Self-Assessment Questionnaire A.
Please note, your merchant bank will still require you to be PCI compliant when using Recurly.js. This means using best practices to secure your servers and payment pages from being compromised with cross-site scripting on your payment page.
Recurly’s Transparent Post API allows you to host your own payment pages with a limited PCI compliance scope. The transparent post API submits the sensitive cardholder data directly to Recurly from your customer’s browser. Since the sensitive cardholder data never passes through your environment, you qualify for the simplest PCI compliance level. Using Recurly’s Transparent Post API has the same complexity as Recurly’s API.
Please note, your merchant bank will still require you to be PCI compliant when using our Transparent Post API. This means using best practices to secure your servers and payment pages from being redirected to another server or compromised with cross-site scripting on your payment page. As long as your payment pages submit directly to Recurly, your network PCI scope will be dramatically limited when compared to using the API only.
Merchants using Recurly’s transparent post qualify for the shortened PCI DSS Self-Assessment Questionnaire A.
Merchants using Recurly’s API to submit cardholder data qualify for the SAQ C questionnaire. When cardholder data passes through your hosting environment, even though you are not storing it, your systems fall within PCI compliance scope. Your merchant bank will require you to complete the PCI DSS Self-Assessment Questionnaire C.
PCI Best Practices
Host any webpages receiving credit card information on SSL. Cardholder data should never be sent without SSL. Please note, your entire app does not have to be served via SSL. The credit card pages are the only pages required to be transmitted via SSL.
Never log any sensitive credit card data (full credit card number or verification value (CVV/CVC)). Most web apps expose credit card data via their log files and not the database.
Never store any sensitive credit card data (full credit card number or verification value (CVV/CVC)). You may store the first six and last four digits of the credit card number. If there’s cardholder data you do not need, then we suggest not storing it (billing address, expiration date, number, etc).
Protect your customers by keeping your site safe from cross-site scripting attacks.
For more information, please see the PCI Security Standards site. Specifically, the PCI DSS Self-Assessment Questionnaire (SAQ) Instructions and Guidelines is very useful.
Please note: Recurly is PCI-DSS Level 1 compliant as a service merchant provider. We are not a qualified security assessor (QSA). The above information comes without warranty. If you have questions about PCI Compliance, we recommend contacting a QSA.