[ECP-9949] Fix TWINT tokenization#3300
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request reclassifies the TWINT payment method by disabling its wallet status in the configuration and updating its UI component provider to a standard payment method provider. Feedback indicates that the adyen_twint_vault configuration for instant purchase remains inconsistent, as it still utilizes card-specific classes that should be updated to their payment method counterparts to ensure consistency with the reclassification.
| <supports_manual_capture>1</supports_manual_capture> | ||
| <supports_auto_capture>1</supports_auto_capture> | ||
| <is_wallet>1</is_wallet> | ||
| <is_wallet>0</is_wallet> |
There was a problem hiding this comment.
While reclassifying TWINT as a non-wallet payment method is correct to prevent card-related field errors, the adyen_twint_vault configuration for instant_purchase (lines 1739-1740) remains inconsistent. It still references card-specific classes (Adyen\Payment\Model\InstantPurchase\Card\AvailabilityChecker and Adyen\Payment\Model\InstantPurchase\Card\TokenFormatter). To ensure consistency and avoid potential issues during the instant purchase flow, these should be updated to use the PaymentMethods counterparts, similar to other non-wallet methods like PayPal or Klarna.
|
3 participants
Description
This PR reclassifies TWINT as a non-wallet payment method to prevent vault token errors caused by missing card-related fields in the Adyen response.