-
Notifications
You must be signed in to change notification settings - Fork 42
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
PayPal: Remove Vault Listener Pattern #308
base: main
Are you sure you want to change the base?
Conversation
analytics.notifyVaultAuthChallengeFailed(request.setupTokenId) | ||
vaultListener?.onPayPalWebVaultFailure(result.error) | ||
} | ||
|
||
is PayPalPresentAuthChallengeResult.Success -> | ||
analytics.notifyVaultAuthChallengeStarted(request.setupTokenId) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in iOS, we just have "challenge-required" event before launching a web view.
So if we wanted to track success/failure of the entire 3ds flow including the web view launch, we would have a starting point.
I guess Android equivalent is "challenge-received" so you just have an extra "start" on the auth.
Summary of changes
PayPalClient
vault flow away from the listener pattern.PayPalWebCheckoutClient.vault()
with calls toPayPalWebCheckoutClient.finishVault()
to complete a vault flowChecklist
Authors