Update Aft and Googlepay and Applepay in payment sessions and Payment Request #452
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 enhances the payment processing capabilities by adding support for new authentication methods, additional configurations for payment sessions, and improvements to request structures.
Changes Made
Payment Processing:
aft
to thePaymentProcessing
class, enabling support for advanced features.ReconciliationQueryPaymentsFilter
to set a default limit of 500 for better consistency.Preferred Experiences:
PreferredExperiences
to support authentication preferences, such as:GOOGLE_SPA
THREE_DS
Authentication and Payment Requests:
Authentication
class to handle preferred experiences during payment authentication.PaymentRequest
to include:authentication
: Supports advanced authentication flows.authorizationType
: Defines the type of authorization used.Payment Sessions:
Applepay
andGooglepay
classes, each with astorePaymentDetails
property.PaymentMethodConfiguration
to include configurations for Apple Pay and Google Pay.Unit Tests:
GOOGLE_SPA
andTHREE_DS
).Authentication
object in payment authorization flows.Impact
Additional Notes