After much beating my head against the wall I discovered this was a known issue. So one could call this a documentation issue (since I couldn't find it anywhere in the module docs or on the civicrm.org module listing), but it sounds like from previous comments it's at least possible this could come in the future.

References:

"Try out Webform Payments and other new features," "Any on-site credit-card processor supported by CiviCRM..." (emphasis added)

"Webform Payments show problems with Paypal Button," "Sorry, but Paypal STD is not yet supported by Webform-CiviCRM Integration."

Again I'm mostly just adding this so that when others go searching for some explanation why it's not working they'll run across this. But this issue could also be used for future development work, if this feature does get started.

CommentFileSizeAuthor
#18 improvepaypalipnsupport-2286503-18.patch1.19 KBTomTech
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

colemanw’s picture

colemanw CreditAttribution: colemanw commented

I would encourage you to update the documentation wiki page to reflect this - I think it would help others in your situation.
http://wiki.civicrm.org/confluence/display/CRMDOC/Webform+CiviCRM+Integr...

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
CreditAttribution: rootwork commented

I've updated the wiki page for the upcoming version and the 4.4 version (which didn't have a payments section at all). I also noted the incompatibility with Stripe, which I discovered in another issue.

I think it might be nice to include at least the on-site payment requirement (and explain that that excludes PayPal Standard) in the "caveats" section of this module.

I'll leave this as a feature request in hopes that it gets explored in the future.

colemanw’s picture

colemanw CreditAttribution: colemanw commented

I've updated the project description to add the caveat about on-site payment processors.

sluc23’s picture

sluc23 CreditAttribution: sluc23 commented

Hi sorry if it's a silly question, but what do you mean by "on-site" payment processors?

Thanks for the clarification

colemanw’s picture

colemanw CreditAttribution: colemanw commented

This means the user enters their credit card details directly in the form on your website, rather than being redirected to e.g. paypal's website.

upperholme’s picture

upperholme CreditAttribution: upperholme commented

I'm not sure whether support for off-site payment processors like Paypal's Website Payments Standard, and also the SagePay payment processor, is something that is on the road map for the future of this module, or if it's simply not do-able? If it's do-able but stalled due to lack of funding support my guess is that there would be a fair number of users that would chip in for such a feature.

colemanw’s picture

colemanw CreditAttribution: colemanw commented

Great news folks! Amnesty Intl. has stepped up with full funding for this issue. Expect to see progress this week.
http://wiki.civicrm.org/confluence/display/CRM/Amnesty+International+Spa...

colemanw’s picture

colemanw CreditAttribution: colemanw commented
Title: Webform CiviCRM contribution/membership does not work with PayPal Website Payments Standard » Support IPN-based payment processors
Assigned: Unassigned » colemanw
rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
CreditAttribution: rootwork commented

Awesome, that's great news! Thanks Amnesty!

upperholme’s picture

upperholme CreditAttribution: upperholme commented

Indeed excellent news. This will make a big difference to many of the organisations I work with, enabling them to really make full use of webforms. Can't wait to hear more news.

upperholme’s picture

upperholme CreditAttribution: upperholme commented

Eagerly awaiting news on this development.

Something crops up that might be within scope: on a webform where a payment is being taken and where a case is being created or updated, would it be feasible to have the contribution filed to the case?

seascoot’s picture

seascoot CreditAttribution: seascoot commented

Very pleased to hear about possible support for PayPal Website Payments Standard. I wonder if this would also extend to offsite hosted payments pages support. That would certainly help with some of the PCI compliance headaches.

upperholme’s picture

upperholme CreditAttribution: upperholme commented

Hi seascoot
As I understand it Paypal standard is an offsite hosted payment page. Presumably if you are working with a payment service thatis offsite, almost by definition the PCI headache is theirs and not yours?

seascoot’s picture

seascoot CreditAttribution: seascoot commented

@upperholme

Offsite payments definitely reduces the burden for PCI significantly, put you're still supposed to do a PCI audit and be compliant if you accept online payments, even if they're processed off-site.

I'm hoping the changes will be more generalized to other processors besides PayPal.

upperholme’s picture

upperholme CreditAttribution: upperholme commented

Thanks for this seascoot - I thought that if the users card data never touches your server you were outside of the scope of PCI compliance, but perhaps I'm wrong on that and will check (any pointers as to a solid and readable source of authoritative guidance on that issue?).

In terms of the changes to webform_civicrm, my understanding is that the primary focus will be on supporting the IPN based payment system used by the organisation funding the development work (see the wiki page referenced at the top of this thread for the details, but I believe that the goal will be to support a wider range of IPN based processors.

colemanw’s picture

colemanw CreditAttribution: colemanw commented

Update: after some delays, work is proceeding on the ipn branch.

  • colemanw committed 112b2af on 7.x-4.x 
    Issue #2286503 - Add basic support for IPN payment processors
  • colemanw committed a24af7e on 7.x-4.x
    Issue #2286503 - Support PayPal button
  • colemanw committed a31a612 on 7.x-4.x
    Issue #2286503 - Show all payment processors
TomTech’s picture

TomTech CreditAttribution: TomTech commented
FileSize
improvepaypalipnsupport-2286503-18.patch1.19 KB

This patch improves the support for PayPal Standard by setting the amount, item_name, and a few other parameters.

This gets you TO the paypal page, but I'm foreseeing an issue upon return.

The IPN is going to post back with the contributionID, not an eventID, so the status of the Participant won't pass through the BaseIPN code that moves it to "Registered" status.

colemanw’s picture

colemanw CreditAttribution: colemanw commented

Hey Tom, thanks so much for the patch. If you have the ability to submit it as a pull request I generally find those easier to collaborate on (but if not, no worries).

  • colemanw committed 69b1d62 on 7.x-4.x 
    Issue #2286503 - Fix paypal ipn redirect location
  • colemanw committed c94f931 on 7.x-4.x authored by TomTech
    Issue #2286503 - Add missing params to ipn checkout
  • colemanw committed ecf3559 on 7.x-4.x
    Issue #2286503 - Handle invoice_id for ipn processors
colemanw’s picture

colemanw CreditAttribution: colemanw commented

Applied Tom's patch and did a bunch more work to get PayPal standard working seamlessly with webforms. Try it out in the latest -dev!

sonicthoughts’s picture

sonicthoughts CreditAttribution: sonicthoughts as a volunteer commented

Would this support allow recurring payments with paypal pro (which uses IPN i believe)

colemanw’s picture

colemanw CreditAttribution: colemanw commented

Recurring payments are not currently supported by this module. I think there's another issue for that open somewhere, but would require someone to sponsor the improvement to get it going.

colemanw’s picture

colemanw CreditAttribution: colemanw commented
Status: Active » Fixed
TomTech’s picture

TomTech CreditAttribution: TomTech commented

Coleman,

First, thanks for making an awesome module. Appreciate the depth of integration and ease of use!

IRT the patch, I'll do a pull request going forward.

I was just wondering since you marked this fixed...when I worked through the code previously, it was not setting the event participants to registered during the IPN callback. Was that addressed elsewhere, or is that still outstanding?

colemanw’s picture

colemanw CreditAttribution: colemanw commented

CiviCRM core should be handling that piece of it, at least for single-event scenarios; haven't tested multiple.
If you find it's still not working in the latest -dev, pls create a new issue for that (and any debugging you can do would be most appreciated).

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

supportbb’s picture

supportbb CreditAttribution: supportbb commented

We are getting same issue with event participants are not registering when paying via PayPal Standard.

Their status left as "Not Completed" while payment was processed successfully by PayPal site. Also there is no contribution created in contact's card in CiviCRM,

we are using webform_civicrm_7.x-13 with civicrm 4.6.8, webform 7.x-4.10