Recurly

PCI-DSS Compliance

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.

Regardless of your Recurly integration, your merchant bank account will still require you to be PCI compliant, so please be aware of the following updates to PCI DSS:

Beginning January 2014 as optional and becoming mandatory as of January 2015 is a key change to PCI DSS for our Hosted Payment Page and Recurly.js customers. The new version of PCI DSS, version 3.0, clarifies many compliance issues and introduces SAQ type A-EP. It will serve as a replacement for SAQ type A, the preferred SAQ for a merchant that uses Recurly’s Hosted Payment Page or Recurly.js.

Recurly.js

Recurly.js is our open-source Javascript library that gives you great looking credit card forms to securely create subscriptions, one-time transactions, and update billing information for your customers. The order forms are designed to be fully customized and hosted on your own servers. Like Transparent Post, the cardholder data passes directly from the customer’s browser to Recurly. Because the cardholder data does not pass through your servers, your PCI scope is limited.

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.

Regardless of your Recurly integration, your merchant bank account will still require you to be PCI compliant, so please be aware of the following updates to PCI DSS:

Beginning January 2014 as optional and becoming mandatory as of January 2015 is a key change to PCI DSS for our Hosted Payment Page and Recurly.js customers. The new version of PCI DSS, version 3.0, clarifies many compliance issues and introduces SAQ type A-EP. It will serve as a replacement for SAQ type A, the preferred SAQ for a merchant that uses Recurly’s Hosted Payment Page or Recurly.js.

Transparent Post

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.

Regardless of your Recurly integration, your merchant bank account will still require you to be PCI compliant, so please be aware of the following updates to PCI DSS:

Beginning January 2014 as optional and becoming mandatory as of January 2015 is a key change to PCI DSS for our Transparent Post customers. The new version of PCI DSS, version 3.0, clarifies many compliance issues and introduces SAQ type A-EP. It will serve as a replacement for SAQ type A, the preferred SAQ for a merchant that uses Recurly’s Transparent Post.

API

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

Additional Notes

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.