Payflow Pro module for Satchmo?

Issue #1324 resolved
dubs
created an issue

So i built my first eCommerce website and am approved for the merchant account. However they want me to use Payflow Pro and there are no modules made for it in Satchmo.

Does anyone have a module for Payflow Pro?

If not how do i go about creating one? I am not very experienced with this stuff and this is my first time using Python Django ever.

Comments (9)

  1. Nan

    I recommend looking at the Authorize.Net payment module, as the APIs are very similarly structured. Examining the API documentation for Authorize.Net and Payflow Pro will help you understand what is the same and what you'd need to change.

    I will probably be building a Payflow Pro module some time soon, but I can't promise when that will be or whether it will be ready in the timeframe you need it. If you do make some progress, I'd love to collaborate.

  2. Anonymous

    I'll start working on this probably next week on my fork and send a pull request. Or is this too specific for satchmo, and is better off as an external app?

  3. Tomas Neme

    that's me up there ^

    I'll start working on this probably next week on my fork and send a pull request. Or is this too specific for satchmo, and is better off as an external app?

  4. Chris Moffitt repo owner

    You can certainly fork it and we will consider pulling in to Satchmo. The only thing I'd ask is that you're willing to help out in the future if there are problems with the module.

  5. Chris Moffitt repo owner

    You can certainly fork it and we will consider pulling in to Satchmo. The only thing I'd ask is that you're willing to help out in the future if there are problems with the module.

  6. Tomas Neme

    Question: I notice that the calls to processor.record_[payment|authorization|failure] are only made on if not testing blocks.

    Why is this? What's the design decision here, exactly?

    Because the success ProcessorResult instance is returned nevertheless, so the order appears as paid for anyways, so I'd like to understand the whole idea.

    A possibly undesired side effect of this is that the ProcessorResult instance doesn't have a Payment instance, and sometimes that might lead to missing data on later steps of the payment.

  7. Log in to comment