Along with several partners of mine, we are entering the processing and security world with a new concept, www.myvirtualcard.com.
The idea is based around a Phone Verification system. Currently, we are working with Visa, and starting talks with other credit card companies about verifying users via a phone system.
Basically, the idea is that when a user goes to make a purchase, our system will call them up, and they will have to enter in a password. This phone number of course, is kept on record, and we will also be able to verify this with the credit card companies, sort of like address verification.
The idea behind this is to deter and lower chargebacks and fradulent charges. In tests we have done on the system, and using data used from other arenas of deployment, the system has been shown to be highly effective in stopping fraudulent use. While we can't eliminate 100% fraud charges or chargebacks, with our system, we can make great strides in doing so.
As the lead developer on the project, and a partner, I am looking for some input into how to make this service more attractive to webmasters on the internet.
What do you recommend as being the API for the service? Currently, I will be implementing it in both normal HTTP Post over SSL, as well as setting up a SOAP implementation. Are their any other standards I should support?
I want to setup some modules for users to easily download and employ, so if you are using PHP or .NET, you can download premade objects that will do the interfacing for you. I had other suggestions to offer Perl as well, and possibly Java. Any other implementations?
We will be offering two types of services. A complete credit card processing service, as well as a phone verificaiton service alone. Do you see a need to seperate anything else out?
I am also looking for any questions you might have concerning the product and services. What things would concern you as a webmaster in implementing this technology? I am primarily concerned with the technical side of the field, however, I would also like some answers regarding whether you would switch your entire processing from your current CC provider to mVC, or would you simply implement the phone verfication.
Thank you for your time. I look forward to your input.
The idea is based around a Phone Verification system. Currently, we are working with Visa, and starting talks with other credit card companies about verifying users via a phone system.
Basically, the idea is that when a user goes to make a purchase, our system will call them up, and they will have to enter in a password. This phone number of course, is kept on record, and we will also be able to verify this with the credit card companies, sort of like address verification.
The idea behind this is to deter and lower chargebacks and fradulent charges. In tests we have done on the system, and using data used from other arenas of deployment, the system has been shown to be highly effective in stopping fraudulent use. While we can't eliminate 100% fraud charges or chargebacks, with our system, we can make great strides in doing so.
As the lead developer on the project, and a partner, I am looking for some input into how to make this service more attractive to webmasters on the internet.
What do you recommend as being the API for the service? Currently, I will be implementing it in both normal HTTP Post over SSL, as well as setting up a SOAP implementation. Are their any other standards I should support?
I want to setup some modules for users to easily download and employ, so if you are using PHP or .NET, you can download premade objects that will do the interfacing for you. I had other suggestions to offer Perl as well, and possibly Java. Any other implementations?
We will be offering two types of services. A complete credit card processing service, as well as a phone verificaiton service alone. Do you see a need to seperate anything else out?
I am also looking for any questions you might have concerning the product and services. What things would concern you as a webmaster in implementing this technology? I am primarily concerned with the technical side of the field, however, I would also like some answers regarding whether you would switch your entire processing from your current CC provider to mVC, or would you simply implement the phone verfication.
Thank you for your time. I look forward to your input.