Troubleshooting - Paylead

Common symptoms when integrating the Paylead WebApp over SSO, and how to resolve them. Most issues trace back to session durations or WebView configuration.

Blank or grey WebApp area, no error

Possible cause:

The WebApp is embedded in an HTML <iframe> rather than a native WebView (see WebView configuration).

How to confirm:

A cookie problem shows the authentication screen. This one shows an empty area.
Look at the asset requests rather than the document URL. Unauthenticated subresources are redirected to the identity provider too, so /assets/*.js answering with a redirect is the signal.

Fix:

Move the integration to a native WebView.

Authentication screen shown frequently

Possible causes:

Partner IdP session expired → adjust its duration so it is ≥ the Paylead IdP session.
Cookies not persisted → check the WebView configuration.
WebView recreated on each open → reuse the same instance.

Authentication screen shown during activity

Possible causes:

The activity generates no server requests → set up a “keep-alive”.
Cookies not sent on some requests → check withCredentials.

Unexpected behaviour or hard-to-diagnose support cases

Possible cause:

The User-Agent does not contain the PayleadWebView suffix.

Fix:

Keep the device’s default User-Agent and append PayleadWebView at the end (see User-Agent identification).

What’s next

Bridge releases

Every published Mobile Bridge version, with the schema download.

API reference

Browse the Program API endpoints and download the OpenAPI specs.

⌘I