One feature that would really come in handy is a coupon code field. Currently the only way I can think to accomplish this is to add a new field to the form that we can validate and adjust our price field with, however I was thinking that this feature would be pretty widely used if it existed.

Overall I am loving the simplicity of this module -- it has really come in handy on sites where uc would just be overkill. Thanks for taking the time to put it together.

Comments

quicksketch’s picture

quicksketch
he/him
commented

I probably won't be adding support for coupon codes to Webform Pay. Once you start trying to cover "typical" e-commerce purposes it's all downhill (coupon codes, recurring payments, sales, carts, etc.)

WillHall’s picture

WillHall commented

I can appreciate that, thanks for your response.

DrewMathers’s picture

DrewMathers commented

You might be able to this by using Webform Conditional to substitute different payment fields depending on the choice of a coupon option. You would then have to use the regular expression or PHP validation methods in Webform Validation to validate the coupon code.

allie micka’s picture

allie micka
she/her
commented

A coupon code payment method would also be a valuable feature for the Payment API proper, as it would be useful for a variety of non-webform payment transactions (e.g. signing up for a site, registering for an event, etc.) That sort of thing is definitely in Pay's bailiwick, as is recurring payments. "Carty" stuff like inventory/shipping/etc. is where we all must draw the line and defer to a real cart system.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (won't fix)

Yeah, as #2 suggested, other modules might be able to provide this functionality. Webform Conditional probably won't handle it correctly at the moment (since it still submits fields that are hidden), but ultimately this may just require clever usage, or, just a separate component for "Coupon code" that affects the value in some creative way.