#hoangminh-payment-request-button

1 messages · Page 1 of 1 (latest)

empty cliff
#

@lucid fulcrum I'm asking my team but not sure we'll be able to debug something this specific.

lucid fulcrum
#

@empty cliff Thank you very much for your help

empty cliff
#

@lucid fulcrum just to confirm, you purely just use the PaymentRequest button here and Jasonelle does everything for you right? It doesn't convert into some custom iOS view and such, it just uses a webview in the app?

lucid fulcrum
#

To be precisely, we do not use the payment request button out of the box from stripe. We have our custom ui. This is how the flow is:

  • Users go to our page and decide to pay for the service
  • When loading the page, we construct payment intent object, send it to stripe and get a response back. The response will basically tell us if payment wallet is ready or not. If the wallet is ready, we will call an api to backend to generate the client secret and send it to front end.
  • The issue in the ios app is that, the response that we get back from stripe tell us that payment wallet is not ready while it works fine in browsers (chrome and safari)
  • And yes, you are correct, Jasonelle does everything for us.
empty cliff
#

what do you technically use though? SFSafariViewController? WKWebview? UIWebView?

#

This is important as the support of PaymentRequest in those differs

lucid fulcrum
#

I'm using Angular for front end, and asp.net core for backend

#

How do I check which one that is using ?

empty cliff
#

That's something you usually would figure out on your end as the developer. The framework you use should document this. I had never heard of Jasonelle but someone on my team dug into it for a bit and thinks it's using WKWebView based on https://jasonelle-archive.github.io/docs/legacy/agents/ saying

Jasonette Agents are invisible background JavaScript execution environments, internally implemented in WKWebView on iOS and WebView on Android.

WKWebView support for Apple Pay is quite limited. Apple usually recommends using SFSafariViewController instead but Jasonelle doesn't use that.
It's possible for WKWebView to support Apple Pay on iOS devices that are iOS13 or more recent per this doc https://www.wwdcnotes.com/notes/wwdc19/518/ but it's not really canonically documented/certain

lucid fulcrum
#

Thanks for a detailed explanation @empty cliff

#

We are a small startup company. We decided to use Jasonelle to simplify our publishing app process. We have one code base for the web app, and use Jasonelle to convert it into android and ios app.

#

But seems like as our app get more complicated, we should go with the native app route instead. It would create less headache for us in the future

empty cliff
#

that's possible. There are many frameworks like this that work though, so it's plausible you can make it work or ask their team to help you debug this too in parallel

lucid fulcrum
#

Thank you for your help and time @empty cliff If I can come up with a solution, I will def go back and update this thread. Thank you very much