Hi,
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.
--
Regards,
Clifford Ilkay
Dinamis
1419-3266 Yonge St.
Toronto, ON
Canada M4N 3P6
for India I have found Ccavenue a good bet - they only have php and java
interfaces, but there is an open source python interface which works
with django.
--
regards
KG
http://lawgon.livejournal.com
Coimbatore LUG rox
http://ilugcbe.techstud.org/
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
That is true. Most of the payment processors have some sort of hosted
form solution for that. However, there are significant limitations in
those hosted form solutions that may make them unsuitable in some
situations. For instance, we ran into one such limitation recently on a
project where the processor apparently doesn't provide any sort of
"success" or "failure" notification for zero dollar transactions. Why
would you want a zero dollar transaction you might be wondering? Our
client was running a promotion where some initial period was free after
which the normal recurring fees would kick in. Normally, there is an
initial fee and recurring fees. Upon success or failure on the normal
initial fee, we'd get a callback to a view function from the payment
gateway which we'd need to complete the transaction. Completion of the
transaction consists of listing the product and updating the user's
dashboard with the transaction date and the expiry date for the listing.
With the zero dollar transaction, we never got a callback due so we
could do none of those things. We had to manually list the products and
update the user's dashboard for the successful transactions in that
scenario.
To avoid creating a situation in the future where there would have to be
tedious and error-prone manual processing, we recommended to the client
that they don't offer "free initial period" promotions but instead
charge some nominal amount, even if it's one cent. "All listings one
cent" doesn't have quite the same impact as "Free listings" even though
for all intents and purposes, it's the same thing. We've discovered many
other limitations like that, small and large, that really makes the case
for API-level integration, in which case you'd have to go through a PCI
compliance audit. By the way, we've been through it multiple times. For
the most part, it's perfunctory.
-- dz
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
I have used Authorize.Net for years and don't have a single complaint.
For Python/Django interfacing to Authorize.Net, Quantam, or PsiGate I
use quix.pay, which I also wrote: http://pypi.python.org/pypi/quix.pay/
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.