Paypal payment method for ProcessWire shop

[apeisa]

Here you go: https://github.com/apeisa/PaymentPaypal-deprecated

If you are trying to implement this one and not feeling lucky, just ask here.

While developing this I played a lot with latest pw dev and shop modules. Everything worked just like they should - so I will move them out from alpha stage.

[Macrura]

many thanks - will test soon!

[Soma]

Cool. While at it. I got some 'fixes' for shop modules and will pr it as soon as I get to it.

[SteveB]

Here you go: https://github.com/apeisa/PaymentPaypal

That will be handy. A year or so ago I did an API interface using PayPal to send payments to people. Don't imagine it comes up very often but if anybody wants to do that let me know.

[joey102030]

Thanks for this apeisa

Is this module able to handle subscriptions?

Is the return URL able to recognise and handle the different 'payment_status' values in the IPN?

[apeisa]

Nope, nothing to do with subscriptions (just paying the shopping cart items through paypal).

Regarding IPN check, it does verifies from Paypal that payment was made and came from Paypal. I will add more checks there though, at least will validate that order sum wasn't altered at any point.

[joey102030]

Thanks apeisa

I ask about the subscriptions because I've just finished a site (not in PW) which sells diet plans. The plans continue for x number of months, and after initial sign-up require a payment to be taken once a month.

A lot of sites which sell a 'service' rather than a product will often require the payment to be a regular subscription rather than a one-off payment.

Regarding the IPN, Paypal sends all outcomes to the same URL, so it would be useful if the method could decipher whether the payment was successful, cancelled, pending etc.

[apeisa]

Well, Paypal has tons of different APIs and ways of doing things.

This one works like this:

1. Send regular form data to https://www.paypal.com/cgi-bin/webscr

2A. User pays (using paypal or using credit card through paypal - no need to login in that case)

2B. Or user cancels (then redirected to cancel url - it is different from success url)

3. After payment user returns to shop and their return is validated from paypal (that Paypal really has that kind of payment made)

It is very simple actually and 100% tied to shopping cart. Recurring payments would need something different to handle recurring subscriptions etc.

[pwired]

Can anyone show me a few web shops made with processwire ?

Is doing seo for a web shop in any way different ?

[Soma]

http://bag-shop.ch

The others aren't online yet.

[apeisa]

http://www.martanpuoti.fi

[pwired]

Thanks for those 2 links. About bag-shop.ch, if I click on details for a bag, a new web page comes up with a bigger picture and more information. Is that all done with fields, so a field for each details of a bag ?

[Soma]

I'm not sure I understand what details you mean but yes it's all done with fields and child pages.

[videokid]

Interesting...

the discount is done/page? Mark?

any chance you might set-up the bags shop as demo somewhere, so we can browse the back-end how you've done things?

Nice job both!

 - I.

[pwired]

yes it's all done with fields and child pages.

Ok thanks Soma, going to try to reproduce that, my first steps in a pw web shop.

[Soma]

The products variations are done using child pages. So even if only one product it's a child page. That makes thing simple. Note that the shop was done 2 years ago, the pw shop was still in alpha early and there was no repeaters yet. Also there a lot custom and only using the cart of pw shop.

[Macrura]

The products variations are done using child pages. So even if only one product it's a child page. That makes thing simple.

that's exactly how i did the Ohm Speakers store, and also another shop i'm working on;

i like this approach the best if the child products have a lot of their own images, and individual data/specs.

if it were a simpler product then repeaters would probably work ok and maybe be easier for the end user to understand..

[pwFoo]

http://bag-shop.ch

The others aren't online yet.

Nice! I like it

@apeisa:

Why the paypal payment module isn't included to your shop module? Is it stable?

[apeisa]

I haven't had any need for shop since the site I build it two (or was it three) years ago. That's one reason that shop hasn't got any love from my side. I build this paypal module since it was requested so many times. It should work just fine.

I would like to build some of the components again, like better shopping cart, more general payment methods, independent checkout process etc, but not sure if I have time for it (especially since the need on e-commerce had been so little on my day job).

[Nico Knoll]

I would support you if any possible. Would love to have a stable shopping system on PW base (including, taxes, currencies, different porto, etc.). Maybe we could just start with making a list somewhere to collect stuff that needs to be included and stuff that could be included (like stripe checkout or stuff like this). What do you think?

Btw.: I really often need to implement a shop so this would be really great. Maybe we could even raise some money if this allows you to put more work into it (Going to write you a PM)

[pwFoo]

I'm searching for different solutions.

SimpleCartJS (not secure because client side shopping cart without server side verification), Snipcart service (secured with product verification via url during checkout) or jQuery plugin smartcart...

Snipcart looks good. Simple to integrate into a website. But missing simple (pdf, email) invoice...

A nice solution could be a javascript framework like SimpleCartJS (add / remove item, show shopping cart and modify quantity of items) with (only) sendform checkout (send to PW backend to verify values and use defined checkout gateways). 

[digitex]

I love shop for processwire. So far it's coming along nicely. I'm trying to sell downloadable files and I have the shop working up to the point of going to paypal to process payment. I haven't gone further yet because I will need a way to deliver the product once paid for. I'm guessing the thank you return page Apeisa provides could be used to create a download link using the $session->order-id but...could it really be that easy?

[adrian]

I think you should take a look at PayPal's IPN (https://developer.paypal.com/webapps/developer/docs/classic/products/instant-payment-notification/)

Setting this up will allow you to set a field in PW to confirm that the user has definitely paid, then you could safely make use of their order-id by sending them an email with the order-id as a get variable in the URL. Your download script would then check the order-id and make sure the paid flag was set before initiating the download.

I use this script as a starting point for my ipn.php file

https://github.com/paypal/ipn-code-samples/blob/master/paypal_ipn.php

Just add:

include("./index.php"); 

at the top to bootstrap in PW and then inside: 

if (strcmp ($res, "VERIFIED") == 0) {

you can use the PW API to set the paid flag to true etc.

[digitex]

I'm glad I asked. I never really believed it would be that simple. Thanks Adrian, I'll be doing some reading and upgrading on paypal.

[Pablos]

I'm just testing the PayPal payment method, and when I click to return to the site from PayPal, Firefox gives me the following security message:

'Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party. Are you sure you want to continue sending this information?'

When the return page loads, it says 'error when validating your payment.'

The payment was in fact successful.

Just wondering if any kind person knows how I might avoid this.