Self-service resources
Before you contact us
- Checked the Troubleshooting guide for the issue you are seeing
- Verified token claims such as
iss,aud,iat,exp, andjti - Checked browser console and network requests for script, CSP, iframe, or token-route failures
- Confirmed that
nsdk-loader.jsloads from the expected SDK origin - Retested with a fresh Embed Token minted for the current authenticated tenant user
What to include in a support request
Request and error context
Request and error context
Include any
request_id returned in an error response, the exact error message shown in the UI or console, and the approximate time the issue occurred.Embed Token details
Embed Token details
Locally decode the JWT and share only the specific claims relevant to debugging, such as
iss, sub, aud, iat, exp, and jti. Never send the raw Embed Token, the raw JWT, or your Connected App secret.Browser evidence
Browser evidence
Include browser console errors, network failures, and screenshots or copied text that show what happened during loader, iframe, or token-route execution.
Steps to reproduce
Steps to reproduce
Describe the exact user flow, page, and actions required to reproduce the problem, including whether it happens consistently or only in specific tenant-user scenarios.
Environment details
Environment details
Include browser name and version, frontend framework, relevant host application details, and the SDK version or deployment environment you are using.
Contact
- Email: support@narrativebanking.com
- Status page: status.narrativebanking.com