Skip to main content

Estimated Delivery Time

Nium provides the estimated delivery times for payout transactions using the estimatedDeliveryTime field in the Remit Transaction Initiated webhook event.

This lets product, operations, and engineering teams set accurate expectations with end users, track SLA adherence, and act quickly when a payout is delayed.

Knowing the an estimated of when funds will be available helps you:

  • Communicate with customers.
  • Accurately track SLA.
  • Proactively handle exceptions or escalations.

When a payout is created, Nium triggers a Remit Transaction Initiated webhook event (e.g., REMIT_TRANSACTION_SENT_TO_BANK_WEBHOOK). The event includes a estimatedDeliveryTime field.

estimatedDeliveryTime is filled with a UTC timestamp (ISO 8601 format) indicating when funds are expected to be delivered.

The value is calculated based on Nium’s pre-configured rules for each payout corridor. Factors include:

FactorDescription
Routing ConfigurationBased on the clearing scheme optimized for the specific transaction.
Processing Cut-off TimesClearing-specific cut-off timings based on source and destination corridors.
Public Holidays & WeekendsObserved in both the sending and receiving countries.
Partner ConstraintsOperating hours, system maintenance windows, and technical limitations.
note

The delivery estimate reflects how Nium expects the transaction to progress under normal operating conditions.

Using estimatedDeliveryTime​

To get the most value from this field:

  1. Subscribe to payout webhooks
    Ensure you’re integrated with Nium’s webhook infrastructure so you receive the estimatedDeliveryTime value at transaction initiation.

  2. Parse the timestamp
    Use the value to:

    • Display ETA to end users in your transaction UI (product & ops)
    • Trigger alerts for potential SLA breaches (engineering)
    • Compare estimated vs. actual delivery times for SLA reporting (ops & compliance)

  3. Handle missing values
    If the field is omitted or null, reach out to your Nium account representative to confirm corridor coverage.

Example Payload​

{
  "template": "REMIT_TRANSACTION_SENT_TO_BANK_WEBHOOK",
  "systemReferenceNumber": "RT4589947391",
  "estimatedDeliveryTime": "2025-07-22T23:29:33Z",
  ...
}

The estimatedDeliveryTime field uses ISO 8601 timestamp format in UTC. If a delivery estimate cannot be calculated for a specific transaction, the field may be omitted or returned as null.

Service level agreement (SLA)​

The estimatedDeliveryTime field is included in these webhook templates:

  • REMIT_TRANSACTION_SENT_TO_BANK_WEBHOOK
  • REMIT_TRANSACTION_PROCESSING_WEBHOOK (if applicable)

FAQs​

Q: Is the delivery time guranteed? A: No. It reflects Nium’s best estimate based on known routing behavior and partner schedules. Actual delivery may vary depending on external factors.

Q: How is this different from payout status updates? A: This SLA is provided at the start of the transaction and reflects how Nium expects the payout to progress. Statuses like SENT_TO_BANK or PAID indicate actual transaction events.

Q: Can I notify end users based on this SLA? A: Yes. Many clients use this field to inform beneficiaries about expected delivery times. However, we recommend pairing it with real-time status updates for confirmation.

Q: What if the field is missing in my webhook? A: This feature depends on your setup. If the field is missing, please contact your Nium account representative for support.

Resources​