>>No that's not correct. Authorize.NET works just fine processing international Credit >>Cards unless your account is configured not to process them.

I was quoting the tech that replied to me in an e-mail when I was trying to set a test account. Nothing was ever offered from them to configure to allow anything but USD transactions.

>And you need to POST content to Authorize.NET not send it via URL string.
>

Interresting, because I send a URL, and it works just fine for me.


>> In the case of authorize.net, they require you send a URL complete with merchand ID, merchandPassword and the rest of the information on the transaction. Once they receive a properly formatted URL, you get a response on whether the transaction went through or not (if it does not go through, they normally return a reason why it did not go through). In their case they povided sample code in VB script that was easily translatable into Foxpro. I ended up using MSXML2.ServerXMLHTTP to submit the URL. I can only assume that other provider work in a similar fashion. Authorize.net by the way only accepts USA transactions, not canadian, but in our case that was what we needed.
>
>No that's not correct. Authorize.NET works just fine processing international Credit Cards unless your account is configured not to process them.
>
>And you need to POST content to Authorize.NET not send it via URL string.
>
>I've used Authorize.NET with an account opened through MerchantPlus(
>https://secure.merchantplus.com/20/) and this has been a very good arrangement for me. I've gone through 6 or 7 different providers and this has been by far the easiest integration and long term processing experience I've had.
>
>
>+++ Rick ---
>
>+++ Rick ---