On Mon, Mar 7, 2011 at 6:03 AM, CLIFFORD ILKAY <[email protected]> wrote: > You can use whatever you like as long as it has an API and documentation. > We've used SecurePay (an Australian one), InternetSecure, BeanStream, > Authorize.net, and others that I can't remember right now. They all have > their pros and cons. A quick checklist of what to look for: > > * API > > * Documentation - very important > > * Test environment, a.k.a. sandbox - very important. Some have great > restrictions on what you can do in that environment so pay attention to the > details. > > * Which currencies will they process? > > * Which credit cards and which other payment methods will they accept? > > * Fees - the pricing is all over the place and like anything, volume will > get you discounts.
And I can't resist recommending solutions that don't require your to touch the credit card number. If you never had it, you can't be responsible for compromising it. Bill -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
