Following up on the thread 'Flask-Cash' a flask extension "Flask-Payments" has been created http://github.com/LeonigMig/flask-payment My goal over time is into integrate with as many payment gateways as possible, starting with the simple easy to sign up with options such as Paypal, AWS and Google Checkout, and moving onto the likes of Authorise.Net and some of the bank backends for VISA. One tricky element is supporting the 'simpler' gateway flows which do not require SSL, where you send your customer over to e.g. PayPal, and they POST them back when they've got all the details. The first Payment system I've got working, which is PayPal WPP "Express Checkout" is this kind of integration. I've got an example, and I would really appreciate any feedback on anything, but especially the API. http://github.com/LeonigMig/flask-payment/blob/master/examples/hello.py My idea was that a configuration gateway would be specified as the PAYMENTS_API config value, and if you called a method not supported by that gateway you would get a Custom exception. Valid configurations would be described in the documentation, which remains a todo. Any time spent reviewing any of this greatly appreciated, Thanks, Jim.
On 08/12/2010 12:50 PM, JimG wrote: > Following up on the thread 'Flask-Cash' a flask extension > "Flask-Payments" has been created http://github.com/LeonigMig/flask-payment > > My goal over time is into integrate with as many payment gateways as > possible, starting with the simple easy to sign up with options such as > Paypal, AWS and Google Checkout, and moving onto the likes of > Authorise.Net and some of the bank backends for VISA. > > One tricky element is supporting the 'simpler' gateway flows which do > not require SSL, where you send your customer over to e.g. PayPal, and > they POST them back when they've got all the details. The first Payment > system I've got working, which is PayPal WPP "Express Checkout" is this > kind of integration. > > I've got an example, and I would really appreciate any feedback on > anything, but especially the API. > > http://github.com/LeonigMig/flask-payment/blob/master/examples/hello.py > > My idea was that a configuration gateway would be specified as the > PAYMENTS_API config value, and if you called a method not supported by > that gateway you would get a Custom exception. Valid configurations > would be described in the documentation, which remains a todo. > > Any time spent reviewing any of this greatly appreciated, > > Thanks, Jim. > > > Hi, Could you review your example, you don't use the url_for method with the endpoint. Thanks
Ah thanks, updated so I'm not importing anything I don't use. I lifted the boilerplate of the example from Flask-SQLAlchemy; similarly I lifted the tests originally from the Flask-Mail tests, so I'll review there and see if there's anything left over. Cheers, Jim. On 12 August 2010 12:08, Stephane Wirtel <stephane@wirtel.be> wrote: > On 08/12/2010 12:50 PM, JimG wrote: > > Following up on the thread 'Flask-Cash' a flask extension > > "Flask-Payments" has been created > http://github.com/LeonigMig/flask-payment > > > > My goal over time is into integrate with as many payment gateways as > > possible, starting with the simple easy to sign up with options such as > > Paypal, AWS and Google Checkout, and moving onto the likes of > > Authorise.Net and some of the bank backends for VISA. > > > > One tricky element is supporting the 'simpler' gateway flows which do > > not require SSL, where you send your customer over to e.g. PayPal, and > > they POST them back when they've got all the details. The first Payment > > system I've got working, which is PayPal WPP "Express Checkout" is this > > kind of integration. > > > > I've got an example, and I would really appreciate any feedback on > > anything, but especially the API. > > > > http://github.com/LeonigMig/flask-payment/blob/master/examples/hello.py > > > > My idea was that a configuration gateway would be specified as the > > PAYMENTS_API config value, and if you called a method not supported by > > that gateway you would get a Custom exception. Valid configurations > > would be described in the documentation, which remains a todo. > > > > Any time spent reviewing any of this greatly appreciated, > > > > Thanks, Jim. > > > > > > > > Hi, Could you review your example, you don't use the url_for method with > the endpoint. > > Thanks >
And the penny dropped what you actually meant, i've changed the string to
url_for('paypal_express_confirm', _external = True).
Cheers, Jim.
On 12 August 2010 12:21, JimG <j.gumbley@gmail.com> wrote:
> Ah thanks, updated so I'm not importing anything I don't use. I lifted the
> boilerplate of the example from Flask-SQLAlchemy; similarly I lifted the
> tests originally from the Flask-Mail tests, so I'll review there and see if
> there's anything left over.
>
> Cheers, Jim.
>
>
> On 12 August 2010 12:08, Stephane Wirtel <stephane@wirtel.be> wrote:
>
>> On 08/12/2010 12:50 PM, JimG wrote:
>> > Following up on the thread 'Flask-Cash' a flask extension
>> > "Flask-Payments" has been created
>> http://github.com/LeonigMig/flask-payment
>> >
>> > My goal over time is into integrate with as many payment gateways as
>> > possible, starting with the simple easy to sign up with options such as
>> > Paypal, AWS and Google Checkout, and moving onto the likes of
>> > Authorise.Net and some of the bank backends for VISA.
>> >
>> > One tricky element is supporting the 'simpler' gateway flows which do
>> > not require SSL, where you send your customer over to e.g. PayPal, and
>> > they POST them back when they've got all the details. The first Payment
>> > system I've got working, which is PayPal WPP "Express Checkout" is this
>> > kind of integration.
>> >
>> > I've got an example, and I would really appreciate any feedback on
>> > anything, but especially the API.
>> >
>> > http://github.com/LeonigMig/flask-payment/blob/master/examples/hello.py
>> >
>> > My idea was that a configuration gateway would be specified as the
>> > PAYMENTS_API config value, and if you called a method not supported by
>> > that gateway you would get a Custom exception. Valid configurations
>> > would be described in the documentation, which remains a todo.
>> >
>> > Any time spent reviewing any of this greatly appreciated,
>> >
>> > Thanks, Jim.
>> >
>> >
>> >
>>
>> Hi, Could you review your example, you don't use the url_for method with
>> the endpoint.
>>
>> Thanks
>>
>
>