On Sat, Sep 27, 2008 at 6:52 PM, Ruddy Gbaguidi <plugworld at micnes.com>
wrote:> Hi Guys
> On the website, we already accept credit card by sending users to paypal
> website where we have an account.
PayPal does have a service that is more like a traditional merchant
service. I don't know if they have a real API that you can integrate
into your system, however.
> Now, we want to do the same with an IVR where people can call a number,
> enter their credit card number and
> expiration date.
This should be rather easy. Any traditional online merchant account.
When you obtain a merchant account there are (simplified version
follows) two parties involved, the bank that process the transactions
and the gateway that accepts the transactions from the merchant (you)
and sends them to the bank to be processed, in real time.
Authorize.net is a very popular gateway supported by most e-commerce
software. The point is that the Authorize.net API is a very popular
system -- just about any pre-built e-commerce software supports it. It
should be rather simple to create an AGI script which takes the credit
card information and interfaces with the Authorize.net. They publish
many examples and detailed API documentation so this should be a
breeze for any skilled programmer. I strongly recommend that you use
the CVV2 and AVS as a minimal means to reduce fraud.
> But I don't see any service or credit card procession company that
> offers this.
> What I want basicly is a service where I can send the credit card number
> I collected and expiration that and
> their charge the number and give me a status back.
>
> Do you know any company that do this ??
That's exactly the purpose of the Authnet API! Further information can
be found here: http://developer.authorize.net/ Authorize.net also
sells their gateway service under another name (I cant recall it right
now), but everything else is the same. Also, some other gateways
support Authorize.net emulation.
>> Chris Bagnall wrote:
>>> Most credit card processing gateways require you to have the
user's
>>> name and address for AVS verification when you perform customer not
>>> present transactions. Easy enough to do over a website, but a bit
>>> more tricky on the phone.
AVS simply verifies the street number and zip code, nothing else. If I
live at 123 Maple Street in zip code 77099 and I steal the credit card
from someone at 123 Test Ct. in the same zip code I can have things
mailed to me and it will pass AVS. Either way, when you are not
shipping a physical product the rate of fraud rises dramatically --
you should carefully investigate fraud prevention for your system.
Authorize.net provide a service which claims to flag/reduce fraudulent
transactions. One of the merchant services I deal with, CDG Commerce
(I highly recommend them, their customer service is top notch, but I
dont think they will process for a VoIP/calling card service), has
another similar system for no cost.