-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authorization / Order, Capture, Reauthorization, Void #36
Comments
#210 added the option to set the payment action, but I forgot to add the Order option, so we still need to add that and then follow through with the rest of this issue. |
Were you able to fully test an "order" after setting this up? I may have been incorrect in the procedure I mentioned for that. It could be that we actually have to run an Authorization against an order, and then capture that authorization. I'm actually not 100% clear on that myself, so I'll have to review the documentation again on that...unless you were able to fully test an order, and then auth/capture it through WooCommerce already..?? |
Yes, I have tested above functionality and it's working fine. |
Ok, I'm a little confused. It looks like you did have to make some adjustments based on my last comment..?? So then you tested after that adjustment..?? |
Actually I forget to add Authorization for order payment action, I have just add new function for that. |
This guy is trying to use this and getting errors on the DoAuthorization and DoCapture API calls: https://www.angelleye.com/support/scp/tickets.php?id=416 |
Right now both Express Checkout and Payments Pro are hard-coded to run everything as a Sale. We need to tie in options for doing Auth/Order and Capture.
Express Checkout settings page should have option to process orders as Sale, Authorization, or Order.
Payments Pro would have the option to set Authorization or Sale (no Order option for Pro).
Orders or Authorization orders in the WooCommerce Orders screen would then need buttons for Capture, Void, Reauthorize, and these would be hooked up to PayPal's DoCapture, DoVoid, and DoReauthorization API's respectively.
When running these API calls we'll pass in the transaction ID that we got back from PayPal on the original order/authorization. The notes in WooCommerce will need to follow this entire flow, of course, and keep authorization transaction ID's and capture ID's separate from each other in the history.
The text was updated successfully, but these errors were encountered: