ICverify - Gone after July 2016
Posted: Wed Jun 17, 2015 12:00 pm
Judging from previous posts, several of us have integrated ICverify credit card processing into our applications. Unfortunately, I just learned today from their product manager that they will stop selling it at the end of next month and will end support a year later. This is due to the costs of PCI compliance, which I can appreciate.
So, does anyone have experience with an alternative embed-able payment card processing application with the following attributes:
1) Complies with all PCI PA-DSS requirements;
2) Either:
a) Activates an EMV-capable pinpad/cardreader and/or
b) Pops up a window to collect card information
...such that all sensitive card data remains within the credit card processing app, and not the "calling" app;
3) Notifies the calling app of the status of each credit card authorization;
4) Provides a reference number to the calling app, so the original transaction may be voided;
5) Makes provisions for a "Pre-authorized" transaction, also known as a "force", whereby an authorization code has already been provided to the customer and it is entered along with the normal transaction information.
6) Provision to Pop-up a window to view the original transaction when reference number is provided;
7) Allows the main app to initiate settlement of the day's card transactons.
As I understand it, these attributes will enable the main app to operate without touching the credit card data -- thus freeing application developers from the costs and ongoing moving-target requirements of PCI validation.
Any thoughts?
Many thanks,
Mark Z
So, does anyone have experience with an alternative embed-able payment card processing application with the following attributes:
1) Complies with all PCI PA-DSS requirements;
2) Either:
a) Activates an EMV-capable pinpad/cardreader and/or
b) Pops up a window to collect card information
...such that all sensitive card data remains within the credit card processing app, and not the "calling" app;
3) Notifies the calling app of the status of each credit card authorization;
4) Provides a reference number to the calling app, so the original transaction may be voided;
5) Makes provisions for a "Pre-authorized" transaction, also known as a "force", whereby an authorization code has already been provided to the customer and it is entered along with the normal transaction information.
6) Provision to Pop-up a window to view the original transaction when reference number is provided;
7) Allows the main app to initiate settlement of the day's card transactons.
As I understand it, these attributes will enable the main app to operate without touching the credit card data -- thus freeing application developers from the costs and ongoing moving-target requirements of PCI validation.
Any thoughts?
Many thanks,
Mark Z