Paypal https payment module

Create issue
Issue #420 new
ben created an issue

Draft paypal payment module for the website payments pro https interface. UK tested, not sure whether same interface works elsewhere. This is for processing payments through satchmo only, any additional requirements for paypal buttons etc are not included. NB full account approval with paypal has been laborious, returned errors like 'invalid merchant' or 'invalid vendor' should be followed up with Paypal themselves.

Comments (12)

  1. ben reporter

    I had a look on the paypal site, i couldn't see the https interface advertised in the US Payments Pro section. However the name/value pairs don't look so different and google did come back with a https interface guide in the US documentation section which is identical to the UK version. (UK:, US: The https interface is a lot cleaner and simpler than the other api. If someone has a US payments pro system account it's probably worth trying and should only take a few minutes to set up and test through It'll be worth running a live transaction rather than a test one too since the the test transaction only seems to test syntax. I'll put a note into the paypal forum to see if i can get a definitive answer.

  2. Chris Moffitt repo owner

    Do you have any idea how much different this might be from a US (or other nationality) version? I'm curious to see if there is a way to make more generic.

    However, if the different implementations are really different then there's probably not much we can do here.

  3. Former user Account Deleted

    Is there any sort of status on this before I start attempting to roll my own? I've found this library: that I was going to use in my attempt, but if someone has most of this out of the way already, then i won't bother and instead perhaps try to help with this one. (We launch in early October and I need this badly). Currently I can't click on any of the above files though as I'm getting an Nginx not found error.

  4. Former user Account Deleted

    sorry previous comment was lifewithryan at gmail dot com -- i don't believe I have an account on here yet, I'll remedy that soon.

  5. Chris Moffitt repo owner

    There seems to be some issues with the attachments. Anyway, to answer your question, I'm still interested in this patch but I haven't heard from anyone else about how compatible this is with the US paypal version. Any input is appreciated.

  6. ryan headley

    I'm submitting our and our for your review. We are using these in our US project and its talking to Paypal fine. I would include the but the way Paypal requires specific account information, my wouldn't do anyone else any good since they'd have to setup their own paypal sandbox accounts, etc...

    I'm sorry if me uploading these files messes anything up, as I've not used bitbucket before. I can send via email as well.

    Let me know if you'd like me to blank-out my and upload that as well...

  7. ryan headley

    I am attaching our version of the processor: lwr-processor to keep it unique from the file already uploaded.

    I know there are some extraneous/unused imports at the top of this file, we're still cleaning things up.

  8. Former user Account Deleted

    I integrated the lwr-* version with a US paypal account. Currently, I'm only using the sandbox accounts but it appears to be working fine. A few minor changes to the import paths for views/urls etc but otherwise not too much work.

    payment/ log.debug(...., self.paymentmodule.MODULE.KEY) Threw an exception because module has not attr KEY. It does have a 'key' attr though. Not sure if this is a satchmo issue or issue with this processor module.

  9. ryan headley

    I have some updates to the payments pro files i uploaded before. What is the best way to handle it? Shall i just upload them here?

    We found a bug that was causing all transactions to go to the sandbox, and another bug where if the card was submitted with spaced, it would get declined. We've since fixed both issues.

    How shall I get the updated files to you?

  10. Log in to comment