-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CC number visible to samplestore #21
Comments
django-authorizenet implements three types of Authorize .NET APIs: When you are using SIM and CIM APIs, CC data is stored on Authorize.NET servers, which are PCI DSS compliant. Regarding AIM, yes, you have to be PCI DSS compliant, because it involves transmission of credit card data: PCI DSS compliance have different levels: If you don't want to worry (much) about PCI DSS compliance, you should use SIM or Hosted CIM APIs, this way your web server never touches CC data. If you don't store any CC data (AIM, CIM), and just "transmit" it you need to complete Self-Assessment Questionnaire C. All SAQ can be found here: When you are a small business your PCI DSS compliance is checked by the bank with whom you have your merchant account, Here you can read more about PCI DSS compliance: On Sep 10, 2012, at 2:25 PM, jrief [email protected] wrote:
|
When using "Make direct payment" the credit card number is sent via POST request to the customers server. This means that your customer needs a PCI DSS certification. I can't imagine that this is the intended usage for this module.
The text was updated successfully, but these errors were encountered: