#Harry (Wharton)

1 messages ยท Page 1 of 1 (latest)

flat adderBOT
narrow ledge
#

pi_3NfUkY2UFjcl8tHR1MFFHkpC

sage oyster
#

๐Ÿ‘‹ Can you share more details on what you need help with?

narrow ledge
#

our user just created a stripe account on our Connect platform, and tried to use the tap to pay feature, it doesn't work

#

Others have experienced similar issues before, is there a period of time after account creation that the user cannot use tap to pay?

#

payment ID is pi_3NfUkY2UFjcl8tHR1MFFHkpC

sage oyster
#

Do you know what customers saw when they tried to use tap to pay?

narrow ledge
#

our app showed our default failure screen

#

other users can use it fine so it's not us

#

any ideas

sage oyster
#

Did you log any decline message?

narrow ledge
#

checking

sage oyster
#

I think we'll need logs from your mobile app in order to debug this.

narrow ledge
#

I don't think so

sage oyster
#

Ah gotcha.

#

Yeah, logs from the SDK side of things will help here

narrow ledge
#

one second

#

checking

#

but is there some kind of known factor that the user needs to wait 30min-1hr after creating stripe account that they can use tap to pay?

#

I think this might be a issue on Stripe's end because we've encountered same issue with other users before

sage oyster
#

No, not as far as I know. As long as the account is active, they should be able to use tap to pay

narrow ledge
#

is there any information from your end that might be helpful

sage oyster
#

I don't see the payment failure on my end so it looks like the request is failing early in the payment flow

narrow ledge
#

yes

#

it def failed at early flow

#

question is why... is it Stripe's end's problem, or ours?

flat adderBOT
narrow ledge
#

what do you think is the more likely scenario

haughty niche
#

Hi ๐Ÿ‘‹

I'm stepping in as @sage oyster needs to go.

#

We can't really tell anything of what is going on here because the problem does not reach our APIs.

#

There could be a bug in the Tap to Pay functionality but we can't tell until we see the code that is being called and the log lines that it generates.

narrow ledge
#

the user tested again and can use the tap to pay now

#

so it's prob Stripe?

haughty niche
#

We don't know

narrow ledge
#

we didn't make any changes on our end

haughty niche
#

It could also be an issue with network connectivity

narrow ledge
#

the user always have to wait 30 minutes or something after initial regisgtration

#

how do we find out

haughty niche
#

But we don't know unless you capture the logs

narrow ledge
#

this issue has come up mulitple times

haughty niche
#

The information is being generated by the SDK being used (Android or iOS) and those are the logs we would need to investigate

narrow ledge
#

iOS

#

ok and that's investigations from our end, right?