payment module for A2B this time last year. Their terms and conditions make explicit reference to VoIP and prepaid calling-cards, which raised my suspicions.
I never received a response from them when I asked for clarification, despite sending the email 3 times at monthly intervals:
Hi there.
I'm one of the developers of
http://www.asterisk2billing.org/ , which is an
open-source VoIP billing application. A2B already supports three other
payment gateways (Paypal, Moneybookers and Authorize.net), and recently a
bounty has been offered for implementing support for 2co.com too.
Whilst searching for your API documentation I took the time to read
https://www2.2checkout.com/documentatio ... bited.htmlWould you please so kind as to furnish me with your alternate rates and terms
& conditions for "Telephone Service, Long Distance, VoIP or PC-to-Phone
Service" as A2B evidently falls into this category.
Sadly, I'm not convinced you'd be happy to process payments originating from
A2B installations at all, but let me describe our software, so you can
form your own opinion.
A2B was designed as a platform for pre-paid and/or post-paid PC-to-phone
service. In addition to the softphone provided in the A2B web interface, it
can also be used with any SIP, H.323 (and many other technologies) endpoint.
A2B can optionally provide an IVR which prompts for an identification number,
a phone number and then connects the call. This feature debits from the same
balance as the user's VoIP account described above, which may be invoiced
later or pre-paid. The IVR itself can be accessed via a VoIP call or a PSTN
call. This seems as though it might be at odds with your prohibited
product "prepaid phone cards".
I'd appreciate any clarification you can offer on your stance regarding our
product. I'm loath to invest the time necessary to support your payment
gateway if your policy dictates you must rescind access to our users.
Thanks for your time.
With no response from them I found other more promising avenues to keep me busy.