I have never used the Google Checkout or PayPal API to process payments. If there is a way that you can get around “touching” any part of the credit card information and outsourcing their web interfaces, you would want, if there is no clear reason, why I will explain below.
There are several considerations you should take before you “transfer your” credit card gateway.
Firstly, will it be used only internally? Sense, will it be for non-commercial, internal use? The reason I ask is that if it is intended for a commercial product, you will have to go through PA-DSS (formerly PABP or Payment Application Recommendations). This is due to the fact that VISA instructed its buyers and sellers to use only software compatible with PA-DSS / PCI. Therefore, it forces software developers to develop compatible software. To be officially certified and on the PA-DSS list, you will have to pay a hefty fee to an external auditor such as Verizon Business Cybertrust to become fully PA-DSS compliant. To give you an approximate figure, it will probably cost you about $ 15,000 to conduct an audit.
It all depends on how your application and environment are structured. We use ICVERIFY (which is now owned by First Data) to process credit cards. ICVERIFY 4.0.3 is on the approved list. Since our applications relate to Track1,2,3, PAN, release dates, etc. Credit card, we also had to get approval. Boom - comes 15K and an annual listing fee with the PCI Security Council .
The interface of our applications with ICVERIFY is through the REQ-ANS interface, and it is very simple. It is not expensive and can work with several clients at the same time. I recommend that you use ICVERIFY if you decide to go this route.
If you have no reason to process credit cards through an application or server, I suggest that you “outsource” credit card processing to PayPal, Google or another larger company and simply receive a message confirming that the payment was successfully processed. It will make your life much easier if you have this opportunity.
user195488
source share