Many providers now have api's that allow them and not you to store the
actual CC numbers but still allow for recurring transactions. You should
check there first.
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Credit-Card-PCI-compliance-tp4656568p4656640.html
Sent from the OF
Thank you for all the comments and ideas.
Is there a document that would address and confirm my concern and questions
regarding the
local credit card storage?
1.
I have a need to store credit card # on local server to accommodate some
business requirements.
This will enable ONE CLICK order using t
For several years now, I have been working in the area of developing
software to support ecommerce; specifically in the area of supporting
electronic transactions, and risk management.
On Tue, Oct 7, 2014 at 7:59 AM, Mauricio Tavares
wrote:
> On Mon, Oct 6, 2014 at 11:52 PM, Tom Running
> wrote
On Mon, Oct 6, 2014 at 11:52 PM, Tom Running wrote:
> I have questions which regarding PCI compliance.
>
Rule 0: PCI compliance is designed by banks to protect banks
while keeping government regulations away. As far as the merchant is
concerned, it is like riding a motorcycle: when bad thing
I have questions which regarding PCI compliance.
0.
Would someone able to shed some light on how the credit card logic work?
1.
Does it contact the credit card authorize gateway for a small authorize
amount and
void if success. Then captured the final CC amount at the order picking
and shipping
