> For the complete documentation index, see [llms.txt](https://docs.nexusglobalpayments.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexusglobalpayments.org/payment-processing/investigation-and-enquiry/nexus-to-destination-ipso.md).

# Nexus to Destination IPSO

This leg covers delivery of the pacs.008 from Nexus to the Destination IPSO.

<figure><img src="/files/1hygHnbg6OekB9BM1hGA" alt=""><figcaption></figcaption></figure>

### Nexus Investigation Process

If Nexus has not received a Payment Status Report (`pacs.002`) containing a final status (`ACCC`, `RJCT`, or `BLCK`) within four minutes of payment initiation, Nexus will send an Investigation Message (`pacs.028`).

Nexus will continue to resend the Investigation Message at a configurable interval defined by Nexus (for example, every six hours) until a Payment Status Report containing a final status is received. The investigation retry cycle is subject to a maximum duration configured by Nexus (for example, 30 hours).

When Nexus receives a Payment Status Report with a `PDNG` (Pending) status, it will create a Service Desk ticket and assign it to the destination IPSO after a Nexus-defined threshold (for example, 24 hours). If no Payment Status Report has been received for the transaction, a shorter threshold may be applied (for example, one hour) to address the higher-priority scenario of a non-responsive participant.

Service Desk tickets are managed and escalated in accordance with the applicable service-level agreement (SLA).

Upon receipt of a Payment Status Report containing a final status (`ACCC`, `RJCT`, or `BLCK`), any related Service Desk ticket will be closed automatically.

In addition, Nexus distributes a six-hourly notification digest containing all unresolved transactions (transactions with no known status and those in `PDNG` status). This digest is provided through the Helpdesk for visibility, case history, and traceability purposes. It is informational only and distinct from Service Desk tickets that require action. Notification digest entries are closed automatically.

### Nexus Scheme Rulebook Requirements

To enable timely transaction finalisation, the Nexus Scheme Rulebook requires IPSOs to respond to all transactions with a Payment Status Report (`pacs.002`) containing a final status.

IPSOs must also support the Nexus Investigation Message (`pacs.028`) and respond with the latest transaction status available to the IPSO.

To prevent unnecessary load on the Nexus Investigation Process, IPSOs are required to reject payment requests destined for PSPs that are known to be unavailable or offline.