Mobile apps
A native mobile app shows myFlowpay in one of two ways. Use the WebView host page if your app can show a WebView page. Use the launch URL only if it cannot.
| WebView host page (preferred) | Launch URL | |
|---|---|---|
| How | A WebView shows a static page from your domain. The page embeds myFlowpay with the Embedded (iFrame) SDK. The app gives the page a signed payload over the WebView JavaScript bridge. | Your backend requests a single-use launch URL. The app opens it in Chrome Custom Tabs or SFSafariViewController. |
| Credential | Signed payload sent by postMessage. myFlowpay accepts it only from your page origin. |
Single-use URL. Until it is used or expires, it signs in any person who opens it. |
| Forwarded link | Nothing to forward | A forwarded URL signs the recipient in to the sender's company. A confirmation page is the only control. |
| Web login in the app | Not necessary. The page holds no session of its own. | Not necessary |
| Session refresh, logout, events | Yes, the full communication protocol | No channel between the app and the browser tab |
| Embed hostname | The same subdomain as the web embed | Optional. If you use one, it cannot be the web embed subdomain. |
| What you build | A static page, a JavaScript bridge, a signing endpoint | A backend call and an in-app browser |
Both options use the same journey and the same webhooks. Flowpay keeps the journey state, so the user continues where they stopped.