#taysonvo-setup

1 messages · Page 1 of 1 (latest)

icy laurel
#

Sounds like a complicated issue. Do you have any pattern to realize other than just Live mode or Android phone?

#

Ie Chrome version? What if you add mounting log and send to some of your backend endpoint?

vast iris
#

We are using android system webview to open the link that contain stripe CC form element.

Initially I not sure what is the error message, because it from frontend library, error will be in console log only, after this I tried to create api on Backend, so when there is any console error on webview it will call that api and send the message that why ai can saw the message

icy laurel
#

I see. The error hints about the Element was somehow unmounted (?) It would be difficult to diagnose without being able to reproduce it

#

So I guess the best you can do is collect more information and try to figure it out the pattern or criteria

#

Did the confirmation call succeeded in the case?

vast iris
#

I tried to reproduce, but hard , still cannot reproduce

#

No, it not reach to the stripe BE in this case

icy laurel
#

It's hard to tell. Maybe try adding some timeout?

#

I don't have anything to offer right now. I think you would want to collect more criteria and write into Support and we will continue supporting in an email thread

#

Please include your integration code as well

vast iris
#

I sent email to Support few days ago, and not getting response after some first clarification, not sure what need to send again.

#

I cannot borrow the phone and the CC that having issue from the customer, so currently what I have is the one I said in the beginning of this conversation 😦

icy laurel
#

Which email did you use in the conversation?

vast iris
#

Initially from the chat support, after this it auto convert to email

icy laurel
#

Okie I found the thread. Will leave an internal note. But really we would need more information so please also try to collect them and reply to the email chain

vast iris
#

I can provide the the code as well

#

will attach on the email, right ?

icy laurel
#
  1. Add a log right before confirming SetupIntent, logging the mounted Element, and then send to your backend
  2. Collect which Android browser is that (Chrome?), which versions?
  3. Include the frontend code
#

And yes send in another email with those information

vast iris
#

"mounted Element" this will content the customer CC info, right ?

icy laurel
#

no, it shouldn't log any CC related info

#

That was important, please make sure to not include any card info in log

vast iris
#

mounted element, I think it having cc info inside, you mean I will have to mask it before send to api ?

dull flume
#

there's no way you can get the raw PAN from our elements so don't worry about it really

#

I'm not sure what my colleague meany really by logging the Element since it's just a DOM component. What's actually important is context like the browser/customer/local IP/SetupIntent IDs

vast iris
#

ok then, how I can get the mounted Element

dull flume
#

yeah don't, just ignore that

vast iris
#

ok

#

local IP ? cannot get it right ?

#

you mean the IP of the device

dull flume
#

you can get it since you're sending a request to your server, it's just the incoming IP on that request

vast iris
#

So I will send it here or via email ? thanks

dull flume
#

email