Forums / Features Wish List / Payment Action: Auth Only Or Final Sale, per product

Payment Action: Auth Only Or Final Sale, per product

Views: 88

Results 1 to 3 of 3
15 Apr 2021, 5:19 PM
#1
shrimp_gumbo_mmmhhh avatar

shrimp_gumbo_mmmhhh

Totally Zenned

Join Date:
Jun 2007
Location:
Texas, USA
Posts:
1,436
Plugin Contributions:
0

Payment Action: Auth Only Or Final Sale, per product

I would love to see this option as being more flexible.... if the item is in stock (Auth Only Or Final Sale) if out of stock (Auth Only or Final Sale).... would open so many doors.... I can hear you.... why not just set it to Auth Only and that takes care of your problem. I had it set there before and that is a big headache trying to make sure the sales are finalized.... if I could sell items that my wholesalers offer but I don't want to bring in...could help sales quite a bit.

23 Apr 2021, 2:17 AM
#2
mc12345678 avatar

mc12345678

Totally Zenned

Join Date:
Jul 2012
Posts:
16,908
Plugin Contributions:
2

Re: Payment Action: Auth Only Or Final Sale, per product

This could be facilitated via observers of the existing code...

The observers in question include (but are not limited to):

  • NOTIFY_PAYPAL_DOEXPRESSCHECKOUTPAYMENT where modification of the calling Classes $values can be modified to address the setting of PAYMENTREQUEST_0_PAYMENTACTION and as necessary ALLOWEDPAYMENTMETHOD. This is supports changes needed in the "before_process" method of the paypal payment method. $order should be available as a global variable allowing parsing of the $order to determine the status of product, though note that at this point in processing, the quantity may have already been reduced by the amount purchased/purchasing (I have not looked into this aspect). With the knowledge of the stock at that state determination can be made about whether the current requested quantity will result in a "delay" or not and whether to authorize the sale or permit final sale.
  • NOTIFY_PAYMENT_PAYPALEC_BEFORE_SETEC where the $options array can be modified to suit the $order that is passed along to that observer. Again this could be used to modify the the settings described in the above observer point, though thankfully the $order is passed along already to perform the review as necessary. This particular notifier is within the easy checkout step 1, so the product has not actually been purchased yet in "normal" flow. Consideration should be given about what "normal" values would be at these locations for each type of payment so that the appropriate settings can be set upon demand. I do note that there are some instructions in some of the files about specific settings that can or can not be set at certain times.

Again, there may be other places, but those are two that I found related to authorization versus immediate purchase/sale and with consideration only of using paypal express. Other paypal variants might operate differently or have need to monitor different notifiers.

In other words, this is something that would be more "plugin" like than base/core code.

ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...

23 Apr 2021, 2:15 PM
#3
shrimp_gumbo_mmmhhh avatar

shrimp_gumbo_mmmhhh

Totally Zenned

Join Date:
Jun 2007
Location:
Texas, USA
Posts:
1,436
Plugin Contributions:
0

Re: Payment Action: Auth Only Or Final Sale, per product

mc12345678:

This could be facilitated via observers of the existing code...

The observers in question include (but are not limited to):

  • NOTIFY_PAYPAL_DOEXPRESSCHECKOUTPAYMENT where modification of the calling Classes $values can be modified to address the setting of PAYMENTREQUEST_0_PAYMENTACTION and as necessary ALLOWEDPAYMENTMETHOD. This is supports changes needed in the "before_process" method of the paypal payment method. $order should be available as a global variable allowing parsing of the $order to determine the status of product, though note that at this point in processing, the quantity may have already been reduced by the amount purchased/purchasing (I have not looked into this aspect). With the knowledge of the stock at that state determination can be made about whether the current requested quantity will result in a "delay" or not and whether to authorize the sale or permit final sale.
  • NOTIFY_PAYMENT_PAYPALEC_BEFORE_SETEC where the $options array can be modified to suit the $order that is passed along to that observer. Again this could be used to modify the the settings described in the above observer point, though thankfully the $order is passed along already to perform the review as necessary. This particular notifier is within the easy checkout step 1, so the product has not actually been purchased yet in "normal" flow. Consideration should be given about what "normal" values would be at these locations for each type of payment so that the appropriate settings can be set upon demand. I do note that there are some instructions in some of the files about specific settings that can or can not be set at certain times.

Again, there may be other places, but those are two that I found related to authorization versus immediate purchase/sale and with consideration only of using paypal express. Other paypal variants might operate differently or have need to monitor different notifiers.

In other words, this is something that would be more "plugin" like than base/core code.

wow! going off of what you have here.... if there was just a plugin that would finalize the sales once they were marked shipped then that would also be great.... how many hours do you think it would take to do a plugin like that? I guess it would be limited to certain payment methods?