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.
2. 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.
3. 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).
4. Get Single Case	GET /issuers/cases/${case_id}	GET	Poll for status on a single case.
5. 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.