Update Payment Request Authentication #438
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces updates to payment request authentication, adding support for advanced authentication options and exemptions, alongside improvements in testing for these new features.
Changes Made
Authentication and Payment Requests:
PaymentRequest
to include:Authentication
: A new property to manage authentication flows usingPreferredExperiences
.AuthorizationType
: Supports specifying authorization types for payment requests.Authentication
class to handle a list of preferred authentication experiences.Enums:
Exemption
enum with new values:OutOfScaScope
,RecurringOperation
,DataShare
,SecureCorporatePayment
.PreferredExperiences
enum with values:GoogleSpa
andThreeDs
.Unit and Integration Tests:
GoogleSpa
.Authentication
integration within payment requests.SubmitArbitrationEvidence
.GetCompiledSubmittedArbitrationEvidence
.Impact
Additional Notes