You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to save a GooglePay Mastercard to vault we see the following failure:
Adyen\Payment\Model\Method\TxVariant::__construct(): Argument #1 ($txVariant) must be of type string, null given, called in ****/vendor/adyen/module-payment/Helper/Vault.php on line 207
It looks like $payment->getCcType() is null; however 'mc_googlepay' is stored in db tables for these payments.
The payment still goes through and order is created, but it causes a 500 error in checkout call to /adyen/carts/mine/payments-details and it appears that the payment has failed; meaning customers are processing the same payment again - it'll fail a second time on mc_googlepay but go through on later attempts with a different Google Pay funding source, or typed card details; but they end up with multiple orders and confirmation emails are async so not getting to them immediately.
Expected behavior
Google Pay Mastercard payments vault correctly and no error is generated
Magento version
2.4.6-p3
Plugin version
9.5.3
The text was updated successfully, but these errors were encountered:
khushboo-singhvi
changed the title
$txVariant is null when trying to vault a Google Pay Mastercard
[ECP-9346]$txVariant is null when trying to vault a Google Pay Mastercard
Jul 23, 2024
We have created an internal ticket to investigate the scenario you mentioned. Our team is looking into it, and we will provide an update as soon as we have more information.
Let me jump into the discussion. This reminds me a configuration issue. Did you enable mc_googlepay and visa_googlepay tx variants on your Adyen Customer Area Payment Methods page? Could you please also confirm that you've enabled all the required additional data fields described on Step 2: Set up recurring contracts in Adyen?
All GooglePay variants seem to be enabled (except one - this is inactive on all our merchant accounts, I believe the team are checking with merchant support as to why it would be inactive); and I can confirm that all additional data is set up correctly.
Thank you for quick response. Then, I can confirm that it might not be a configuration issue. You will be informed when the investigation is completed.
Describe the bug
When trying to save a GooglePay Mastercard to vault we see the following failure:
Adyen\Payment\Model\Method\TxVariant::__construct(): Argument #1 ($txVariant) must be of type string, null given, called in ****/vendor/adyen/module-payment/Helper/Vault.php on line 207
It looks like $payment->getCcType() is null; however 'mc_googlepay' is stored in db tables for these payments.
The payment still goes through and order is created, but it causes a 500 error in checkout call to
/adyen/carts/mine/payments-details
and it appears that the payment has failed; meaning customers are processing the same payment again - it'll fail a second time on mc_googlepay but go through on later attempts with a different Google Pay funding source, or typed card details; but they end up with multiple orders and confirmation emails are async so not getting to them immediately.Expected behavior
Google Pay Mastercard payments vault correctly and no error is generated
Magento version
2.4.6-p3
Plugin version
9.5.3
The text was updated successfully, but these errors were encountered: