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, whi
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
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
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 goi
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 respons
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
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
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
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
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
10 matches
Mail list logo