Hi,
I’m building a booking system for a small stretch studio in Japan. The seller connects their Square account to our app with OAuth. Members save a card once from their phone, and our server charges it once a month with CreatePayment (we’re not using the Subscriptions API).
Most customers open our pages from the shop’s LINE official account, so the card form will usually run inside LINE’s in-app browser (WKWebView on iOS, WebView on Android). I couldn’t find these in the docs:
- Does the Web Payments SDK card form, including the 3DS challenge when storing a card (intent STORE), work inside an in-app WebView like LINE’s? Any known issues? If it isn’t supported we’ll send people out to Safari/Chrome, so I’d like to know before building it.
- We’ll need extra permissions later for cards on file. When the seller re-authorizes with the new scopes, what happens to the existing access token and refresh token? Do they keep working until they expire, or are they revoked right away?
- If 3DS fails while storing the card, what’s the recommended way to handle it? Is showing an error and letting them retry enough, or should we limit retries / wait before retrying?
Thanks!