Skip to content
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

Adyen: Add support for Pan Only GooglePay #5221

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

almalee24
Copy link

Remote
146 tests, 469 assertions, 12 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 91.7808% passed

If it is a Pan Only GooglePay then pass 'paymentdatasource.type and selectedBrand as googlepay and paymentdatasource.tokenized as false

@almalee24 almalee24 requested a review from a team August 16, 2024 18:19
Copy link
Contributor

@bradbroge bradbroge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like there is a lingering pry, other than that it looks good.

@@ -1,3 +1,4 @@
require 'pry'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be removed.

post[:additionalData]['paymentdatasource.tokenized'] = options[:wallet_type] ? 'false' : 'true' if selected_brand == 'googlepay'
end

return if options[:skip_mpi_data] == 'Y' || options[:wallet_type]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is wallet_type a gsf, or where is it coming from? If so is there a chance that a customer would send this with a NetworkTokenizationCreditCard and we would skip mpiData in a case where we might not want to?

Copy link
Author

@almalee24 almalee24 Aug 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wallet_type get's passed by us for non-tokenized GooglePays which would be a CreditCard in AM. That's why we want to skip it because they wouldn't have cryptogram or eci.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! That is perfect, just making sure it couldn't be passed by mistake on regular CCs.

Copy link
Contributor

@bradbroge bradbroge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻 Awesome work as always!

Remote
146 tests, 469 assertions, 12 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
91.7808% passed

If it is a Pan Only GooglePay then pass 'paymentdatasource.type and selectedBrand as googlepay
and paymentdatasource.tokenized as false
@almalee24 almalee24 force-pushed the adyen_google_pay_non_tokenized branch from a75bbe9 to 1f4030f Compare August 28, 2024 17:40
@almalee24 almalee24 merged commit 1f4030f into master Aug 28, 2024
5 checks passed
@almalee24 almalee24 deleted the adyen_google_pay_non_tokenized branch August 28, 2024 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants