---
sourceDocument: Australia Financial Services Operations
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/financial-services-operations

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Reference

# Financial Services Operations Integration with Verifi reference {#ariaid-title1}

Release version: Australia  
Updated April 7, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Learn about other supporting information that can help you configure and use the Financial Services Operations Integration with Verifi application.

* [JWT Authentication](https://www.servicenow.com/docs/f3CE2jbso_lrdA~y9d10rg "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.")
* [API Subflows and Endpoints](https://www.servicenow.com/docs/QWHpnDjzRGuMR~R4W9AuGg "The application is built on four sequentially orchestrated subflows. Each maps to a specific Verifi REST endpoint and triggers at a defined point in the dispute workflow.")
* **[JWT Authentication](https://www.servicenow.com/docs/f3CE2jbso_lrdA~y9d10rg)**   
  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.
* **[API Subflows and Endpoints](https://www.servicenow.com/docs/QWHpnDjzRGuMR~R4W9AuGg)**   
  The application is built on four sequentially orchestrated subflows. Each maps to a specific Verifi REST endpoint and triggers at a defined point in the dispute workflow.