-
Notifications
You must be signed in to change notification settings - Fork 662
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
How to close Secure Checkout when needed #2478
Comments
@abedsh thanks for filing. By "Secure Checkout" do you mean the 3DS2 challenge screen? |
Correct
…On Wed, May 13, 2020, 9:40 AM Michael Shafrir ***@***.***> wrote:
@abedsh <https://github.com/abedsh> thanks for filing. By "Secure
Checkout" do you mean the 3DS2 challenge screen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADSODGIVQZGKS7C7DON6R43RRKPL7ANCNFSM4M6OGOGQ>
.
|
@abedsh does configuring a timeout as explained in https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure work for you? |
Thank you, this can help but will the form dispatch any event that I can
listen to when it closes ?
…On Wed, May 13, 2020 at 10:48 PM Michael Shafrir ***@***.***> wrote:
@abedsh <https://github.com/abedsh> does configuring a timeout as
explained in
https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure work for
you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADSODGIG6EDLBTFC45BOTV3RRNLXHANCNFSM4M6OGOGQ>
.
|
You can be notified of the event in |
I have successfully configured a PaymentAuthConfig with a timeout , the
challenge screen is closing accordingly, but I am not receiving any event
on onActivityResult() . This also applies to when the user closes the
challenge screen by pressing on the cancel button
Test was made on card (4000000000003220)
…On Thu, May 14, 2020 at 10:47 AM Michael Shafrir ***@***.***> wrote:
You can be notified of the event in onActivityResult() via
Stripe#onPaymentResult(). The outcome value will be Outcome.TIMEDOUT.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADSODGIZSXDFPX6KYDBSQULRRP77PANCNFSM4M6OGOGQ>
.
|
@abedsh can you share code so I can see your implementation? |
@mshafrir-stripe sure,
|
Use PaymentIntentResult#getOutcome(), and then compare the value against the Outcome constants. Specifically, Outcome.TIMEDOUT. |
@mshafrir I am not even receiving any events that triggers a call to onActivityResult when the form closes by itself on timeout |
@abedsh I can't reproduce this issue - I get a callback when I cancel the 3DS2 challenge screen. Can you try reproducing with our example app? |
@mshafrir-stripe I am not sure if all the test card are supposed to behave the same, I just need a way to consistently tell when a challenge screen is closed either by the user or automatically (by time out) so I can probably integrate it in the payment flow of my app With card (4000002500003155):
With card (4000000000003220):
|
@abedsh in your example, what is the superclass of |
@mshafrir-stripe PackageOrderStripePaymentWorkflow is a Fragment with a BottomSheetDialogFragment parent |
There is a bug where the 3DS2 challenge flow is launched from the Fragment's Activity instead of from the Fragment itself. This was fixed in #2494 but hasn't been released yet. In the mean time, you can override |
Summary
Is there a way to check if the Secure Checkout form has opened so I can handle session time out on the app by closing it in case the user is idle on it for a specific period of time ?
Code to reproduce
I am following the basic accept payment tutorial with the test card that triggers the secure checkout process (4000002500003155)
Android version
21+
Impacted devices
no
Installation method
Gradle
SDK version
14.4.0
Other information
The text was updated successfully, but these errors were encountered: