Skip to main content
G
gamandes
October 7, 2024
Question

PCI compliance, self-employed freelancer.

  • October 7, 2024
  • 1 reply
  • 0 views

I keep getting emails about PCI compliance. I do not accept credit card payments outside of one client who pays me through QB with a credit card. I don't understand why I need to pay a fee to an outside vendor for this compliance if QB is the only place I accept a credit card payment. If this is the case, I will tell the client they can no longer pay by credit card because I'm already losing money in credit card fees. 

If I no longer accept credit card payments through QB do I still need to go through this process? 

1 reply

S
Sherrie_F
October 7, 2024

Yes, @gamandes. Even if you no longer accept credit card payments, you still have to be PCI compliant as long as you've linked QuickBooks Payments in QuickBooks Self-Employed (QBSE). Let me lay down some information on why you keep getting emails about PCI compliance and assist you further with this.

 

Our QuickBooks Payments subscribers meet Data Security Standards (DSS) Compliance requirements because Intuit has a PCI provider. If you've set up QuickBooks Payments account to link with QBSE with Security Metrics, you'll have to complete it.

 

Furthermore, compliance requirements are necessary if you purchase the PCI package from Security Metrics. The PCI package ensures that your business is compliant with the Payment Card Industry Data Security Standard (PCI DSS). This compliance helps protect against data breaches and secure handling of sensitive information.

 

However, if you don't want to use credit card payments and unlink your QuickBooks Payments, that's the certain time that you're no longer require to be PCI compliance.

 

To learn more about PCI data security standard compliance services, I've added this article: Learn about the PCI DSS Compliance Service.

 

You're always welcome here if you have other queries about PCI compliance. It will always be my pleasure to provide assistance.

Terms & ConditionsAccessibility statement