Track Payouts

After you create a payout, the next step is to track its progress. This helps you make sure everything is moving as expected—and take action if needed.

Nium lets you track payouts using the following:

• Nium API
• Nium Portal
• Nium Connect
• Webhooks or Callbacks

Payout Lifecycle

After a payout is created, it moves through a series of statuses that reflect its progress—from initiation to completion.

The final (or terminal) statuses are:

• PAID
• REJECTED
• RETURN

For a full list of possible statuses and what each one means, see Transaction Lifecycle.

Statuses

Below is a list of all possible payout statuses, from start to finish, along with what each one means.

Status	Description
AWAITING_FUNDS	The transaction is waiting for funds to be added.
CANCELLED	The transaction was canceled by the customer. This usually applies to scheduled payouts that haven’t started yet.
COMPLIANCE_COMPLETED	The transaction passed compliance checks and is ready for the next step.
EXPIRED	The transaction expired—usually due to not being funded in time or an expired Foreign Exchange (FX) rate.
FAILED	The transaction failed. Check for issues (like missing funds) before trying again.
IN_PROGRESS	The transaction is currently being processed.
INITIATED	The transaction has been started and is in the processing flow.
PAID	Funds have been sent to the beneficiary from Nium’s partner bank.
PG_PROCESSING	Nium’s payment gateway is processing the payout and finding the best route through the partner bank network.
REJECTED	The transaction was rejected due to compliance rules.
RETURN	The payout was returned by the processing bank, clearing system, or beneficiary bank. This usually happens when something goes wrong on their end.
RFI_REQUESTED	Compliance flagged the transaction and requested more information (RFI).
RFI_RESPONDED	Nium received a response to the compliance RFI.
SCHEDULED	The transaction is scheduled to be processed on a future date.
SENT_TO_BANK	The payout instructions were sent to Nium’s partner bank. Once the partner bank completes the payout, the status changes to PAID.

Sub-statuses

Sub-statuses provide more detail about a payout that reaches the PAID status. They help you understand what stage the transaction is in—whether it’s still with the beneficiary’s bank or has already been credited to the beneficiary’s account.

This added transparency is especially useful for tracking how payouts behave in different countries and regions.

note

PAID means funds were sent from Nium’s partner bank—it doesn't always mean the funds have been confirmed as delivered to the beneficiary. On corridors where the clearing system doesn't return a credit confirmation, Nium can't positively confirm delivery. Use the sub-status below to understand the actual delivery confidence for a given payout.

Status	Sub-status	Description	Delivery meaning to client
PAID	PROCESSED_BY_CLEARING	Processed by the clearing system; Nium has limited visibility into further clearing or partner-side progress.	Sent on a corridor that returns no delivery confirmation
PAID	SENT_TO_BENEFICIARY_BANK	Sent to the beneficiary’s bank. Funds are credited shortly if the account is active and compliant.	Reached beneficiary bank, credit pending
PAID	SENT_TO_BENEFICIARY_BANK_ACCOUNT	The funds have been credited to the beneficiary’s bank account.	Credit confirmed by clearing/partner
PAID	DEEMED_PAID	The window is typically 48 hours but varies by corridor. If no return arrives in that window, Nium treats the payout as delivered.	Return window elapsed with no return; not positively confirmed

A payout in PAID can still move to RETURN at any sub-status except SENT_TO_BENEFICIARY_BANK_ACCOUNT. If that happens, you receive a RETURN status update. Handle it the same way as any other return.

For complete visibility into the transaction trail, consume sub-statuses for all corridors.

Corridors without credit confirmation

Payouts on these corridors only receive the sub-statuses below. They never reach SENT_TO_BENEFICIARY_BANK_ACCOUNT.

Currency	Payout Rail	Sub-status	Reason
NZD	BECS	PROCESSED_BY_CLEARING DEEMED_PAID	Clearing system limitation
CAD	EFT	PROCESSED_BY_CLEARING DEEMED_PAID	Clearing system limitation

Where to get sub-statuses

Sub-statuses are available in:

• Webhook: Remit Transaction Sub-status Update, sent whenever the sub-status of a PAID payout changes.
• API: Fetch Remittance Life Cycle Status, in the subStatus field.