--- title: JWT Authentication description: The Verifi Issuer API uses JSON Web Tokens \(JWT\) for authentication. A fresh JWT must be generated for every API call. This section explains how to store credentials securely and how the ServiceNow script generates and attaches the JWT. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/financial-services-operations/jwt-authentication.html release: australia topic_type: reference last_updated: "2026-04-06" reading_time_minutes: 1 breadcrumb: [Reference, Verifi, Integrate, Financial Services Operations \(FSO\)] --- # JWT Authentication The Verifi Issuer API uses JSON Web Tokens \(JWT\) for authentication. A fresh JWT must be generated for every API call. This section explains how to store credentials securely and how the ServiceNow® script generates and attaches the JWT. |Header|Value Format|Description| |------|------------|-----------| |Authorization|Bearer <encoded JWT>|Base64url-encoded JWT signed with HMAC SHA-256 using the shared secret.| |x-verifi-issuer|<Issuer ID>|Your numeric Issuer ID assigned by Verifi. This value must match the iss claim in the JWT payload.|
| Type | Details |
|---|---|
| Header | ``` { "alg": "HS256", "typ": "JWT" } ``` |
| Payload |
```
{ "iss": " |