API Subflows and Endpoints

reference australia Updated Sep 10, 2026 1 min read api-subflows-and-endpoints.md
Raw file servicenow.com

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.

Subflows

API Endpoint

Method

Outcome

  1. Merchant Eligibility Inquiry

POST /issuers/cases

{inquiryOnly: 1}

POST

Runs automatically in the background when the issuer agent opens the "Review Participating Merchant Alerts" task. No UI action required.

  1. Create Case

POST /issuers/cases

{inquiryOnly: 0}

POST

Runs immediately after a successful eligibility response (HTTP 200), sequentially in the same background flow. Manual fallback UI action available if the backend API call fails.

  1. Get Cases (Poll)

GET /issuers/cases?caseId=${case_ids}

GET

Polls on a configurable interval while the task is in "Awaiting External Info." Terminates when case status = EXPORTING or when the 72-hour SLA window lapses (statusCode 910).

  1. Get Single Case

GET /issuers/cases/${case_id}

GET

Poll for status on a single case.

  1. Update Case

PATCH /issuers/cases/{caseId}

PATCH

Runs once when EXPORTING status is received and the merchant response is stored. Sends {"status": "CLOSED"} as the mandatory issuer acknowledgment handshake. Case is excluded from further polling.

**Parent Topic:**[Financial Services Operations Integration with Verifi reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/referring-financial-services-operations-integration-with-verifi-cdrn.md)
Search documentation
Search document titles and file paths on the australia branch