Re: Payment Gateways

[Micah Carrick]

No problem. ;)

On Fri, Apr 1, 2011 at 4:17 AM, Venkatraman S  wrote:

>
> On Wed, Mar 30, 2011 at 12:19 AM, Micah Carrick wrote:
>
>> 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/
>>
>
> Thanks Micah for this :
> http://www.micahcarrick.com/authorize.net-credit-card-form-django.html ;)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>



-- 
*Green Tackle* - *Environmentally Friendly Fishing Tackle*
www.GreenTackle.com 

 Email: mi...@greentackle.com
 Phone: 971.270.2206
 Toll Free: 877.580.9165
 Fax: 503.946.3106

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[Venkatraman S]

On Wed, Mar 30, 2011 at 12:19 AM, Micah Carrick wrote:

> 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/
>

Thanks Micah for this :
http://www.micahcarrick.com/authorize.net-credit-card-form-django.html ;)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[Micah Carrick]

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/

In testing quix.pay, I found that the Quantam gateway in authorize.net
emulation mode isn't bad. You can choose Quantam as the "free" gateway
with CDGCommerce if you have a lower sales and want to save on the
monthly gateway fee that Authroize.Net charges. Quantam was just a
little slower to respond than Authorize.Net but still quite
reasonable. I've been working on adding Paypal Web Payments Pro and
PayFlow into quix.pay and they certainly do the trick but I still
prefer Authorize.Net.

On Mar 12, 10:32 am, Malcolm  wrote:
> I recently used FeeFighters and they have a really awesome setup to
> help you compare and find merchant processors and gateways.  It's
> pretty neat because the merchant processors "bid" based on your
> preferences and all of their pricing is transparent and easy to
> understand.
>
> As for gateway, I am going with Authorize.net for my project.  PyPI
> has an authorize package for API integration and my developer found a
> django app at:https://github.com/zen4ever/django-authorizenet
>
> If interested in FeeFighters, please consider using my referral 
> link.https://feefighters.com/referral/d61fce3c6c274b38    :-)
>
> Malcolm
>
> On Mar 8, 6:43 pm, David Zhou  wrote:
>
>
>
>
>
>
>
> > I use Braintree, and it's been great.
>
> > -- dz
>
> > On Tue, Mar 8, 2011 at 4:40 PM, CLIFFORD ILKAY
>
> >  wrote:
> > > On 03/08/2011 09:59 AM, Bill Freeman wrote:
>
> > >> 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.
>
> > > That is true. Most of thepaymentprocessors 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 thepaymentgateway 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.
> > > --
> > > Regards,
>
> > > Clifford Ilkay
> > > Dinamis
> > > 1419-3266 Yonge St.
> > > Toronto, ON
> > > Canada  M4N 3P6
>
> > > 
> > > +1 416-410-3326
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Django users" group.
> > > To post to this group, send email to django-users@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > django-users+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[Malcolm]

I recently used FeeFighters and they have a really awesome setup to
help you compare and find merchant processors and gateways.  It's
pretty neat because the merchant processors "bid" based on your
preferences and all of their pricing is transparent and easy to
understand.

As for gateway, I am going with Authorize.net for my project.  PyPI
has an authorize package for API integration and my developer found a
django app at:
https://github.com/zen4ever/django-authorizenet

If interested in FeeFighters, please consider using my referral link.
https://feefighters.com/referral/d61fce3c6c274b38 :-)

Malcolm


On Mar 8, 6:43 pm, David Zhou  wrote:
> I use Braintree, and it's been great.
>
> -- dz
>
> On Tue, Mar 8, 2011 at 4:40 PM, CLIFFORD ILKAY
>
>  wrote:
> > On 03/08/2011 09:59 AM, Bill Freeman wrote:
>
> >> 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.
>
> > That is true. Most of thepaymentprocessors 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 thepaymentgateway 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.
> > --
> > Regards,
>
> > Clifford Ilkay
> > Dinamis
> > 1419-3266 Yonge St.
> > Toronto, ON
> > Canada  M4N 3P6
>
> > 
> > +1 416-410-3326
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django users" group.
> > To post to this group, send email to django-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[David Zhou]

I use Braintree, and it's been great.

-- dz



On Tue, Mar 8, 2011 at 4:40 PM, CLIFFORD ILKAY
 wrote:
> On 03/08/2011 09:59 AM, Bill Freeman wrote:
>>
>> 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.
>
> 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.
> --
> Regards,
>
> Clifford Ilkay
> Dinamis
> 1419-3266 Yonge St.
> Toronto, ON
> Canada  M4N 3P6
>
> 
> +1 416-410-3326
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[CLIFFORD ILKAY]

On 03/08/2011 09:59 AM, Bill Freeman wrote:

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.


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.

--
Regards,

Clifford Ilkay
Dinamis
1419-3266 Yonge St.
Toronto, ON
Canada  M4N 3P6


+1 416-410-3326

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[Bill Freeman]

On Mon, Mar 7, 2011 at 6:03 AM, CLIFFORD ILKAY
 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 django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[Kenneth Gonsalves]

On Mon, 2011-03-07 at 06:03 -0500, CLIFFORD ILKAY 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: 

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/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Payment Gateways

[CLIFFORD ILKAY]

On 03/07/2011 05:01 AM, Venkatraman S wrote:

Hi,

Would like to know which payment gateways do people use for managing
money movements in their sites?
I wouldnt like to go the Paypal way, any other suggestions?


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

<http://dinamis.com>
+1 416-410-3326

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Payment Gateways

[Venkatraman S]

Hi,

Would like to know which payment gateways do people use for managing money
movements in their sites?
I wouldnt like to go the Paypal way, any other suggestions?

-V-

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.