A merchant must always be PCI compliant if they accept credit card payments online (even if the card is entered on another site via Recurly). If you are using Recurly.js V4 or later or Recurly Hosted Payment Pages, Recurly's recommendation is to complete SAQ-A. If you are using Recurly.js (any version earlier than v4), Recurly's recommendation is to complete SAQ A-EP.
If card data passes through a merchant's servers, Recurly recommends SAQ C or SAQ D. A merchant's bank will have the ultimate say for PCI compliance documentation and assessment requirements.
Using our hosted payment pages is the easiest way to start accepting subscriptions 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 (v4) should be eligible to complete the shortened PCI DSS Self-Assessment Questionnaire A.
Please note, your merchant bank account provider 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 provider will still require you to be PCI compliant, so please be aware of the following updates to PCI DSS:
- PCI DSS, version 3.2, clarifies many compliance issues and introduces SAQ type A-EP. SAQ A may be completed by merchants linking to 3rd party payment pages (e.g., Recurly's Hosted Payment Pages) and merchants hosting their payment page while using Recurly.js (v4) to secure the billing details. If merchants are hosting their payment page and using an earlier version of Recurly.js (v3 or earlier) to secure the billing details, they should complete SAQ A-EP. Please see the Understanding the SAQs for PCI v3 (pages 4 and 5) for more information.
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 account provider will require you to complete the PCI DSS Self-Assessment Questionnaire C.
Host any webpages receiving credit card information on TLS. Cardholder data should never be sent without TLS. Please note, your entire app does not have to be served via TLS. The credit card pages are the only pages required to be transmitted via TLS.
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.
Please note: Recurly is PCI-DSS Level 1 compliant as a merchant service 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.
Updated over 1 year ago