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
[Paypal express-checkout-nvp] Inconsistency in Transaction Status Key Naming #988
Comments
@ViniTou The checks are correct. When a payment is initiated, the Payum/src/Payum/Paypal/ExpressCheckout/Nvp/Action/PurchaseAction.php Lines 82 to 101 in c8da4ce
The Payum/src/Payum/Paypal/ExpressCheckout/Nvp/Action/Api/DoExpressCheckoutPaymentAction.php Lines 44 to 46 in c8da4ce
So when the If there is something specific not working for you, please let me know what issues you are facing. |
If there are any other issues, please feel free to re-open the issue and add additional detail |
Thing is I was not talking about capturing payment, as that works fine, but |
Greetings,
I've outlined the logic flow below and would appreciate corrections if any discrepancies are identified:
Incoming Notify Action: Initiates the
\Payum\Paypal\ExpressCheckout\Nvp\Action\PaymentDetailsSyncAction
.Within the
PaymentDetailsSyncAction
, transactions are fetched for each transaction in a loop:The response for these transactions is stored in the model through the
GetTransactionDetailsAction
:Note: Each value is stored under a key with the
PAYMENTREQUEST_
prefix.The complete model is intended to be used with
GetHumanStatus
. However, there appears to be an issue with the checks for transaction status, as they reference values under the wrong key inPaymentDetailsStatusAction.php
:Question: Is there a reason why this setup might not be working, or is it a case of misnamed keys? If the latter, should the key in
PaymentDetailsStatusAction
be updated?Your insights on this matter would be highly valuable. Thank you.
The text was updated successfully, but these errors were encountered: