PCI DSS compliant related to the Mobile Application payment

£可爱£侵袭症+ 提交于 2019-12-04 21:56:53

The standards documentation states that you need to be PCI compliant if you "store, process, or transmit cardholder data". It's clear you transmit card data, hence you need to be PCI compliance.
You can easily avoid being compliant by using a 3rd party hosted payment service where the order page and card capture is not served by your application. PayPal is the most popular example, but there are others like BlueSnap, Zooz, Cybersource, BrainTree, etc.
The effort of becoming PCI compliant is relative to the complexity of your solution. The more software/IT layers the card flows through, the harder it'll be to get compliant. If you implement direct communication between the app and the processor (as you suggested), than it should be pretty easy to become compliant. Basically all you need to do is fill out the self assessment questioner and send it to your processor.

Apart from Tal's answer, it is important to look at the level of your client on PCI level.

http://usa.visa.com/clients-partners/acquirers/data-security/pci-dss-compliance.jsp

The level of PCI requirements that needs to satisfy may change depending on your Merchant's Credit card transaction behavior.

If you prefer to use some of the information ( for loyalty program) for your application, it better to use a VAULT with tokenization implementation. https://www.pcisecuritystandards.org/documents/Tokenization_Guidelines_Info_Supplement.pdf

As a practice, it important have a diagram of data path ( how the information flows ) to understand what vulnerabilities you will come across in your application. This will help to review the security that you need to incorporate in order to protect customer data.

https://www.voltage.com/wp-content/uploads/Voltage_WP_SecureData_Streamlining_InformationProtection_DataCentricSecurityApproach.pdf

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!