Making a Payment (PayOut)

Webhooks are used to notify your application of changes to the status of Agreements, Payment Requests, Credits, Debits, etc as they are processed through the system.

By subscribing to our webhook events you can monitor the status of each transaction, and then trigger the appropriate next steps. While making Payments and Payment Requests, webhooks allow you to check the status of the transactions.

This article gives an overview of the webhook events you would expect to receive for the following scenarios.

Making a Payment

Overview

When a dispute is raised by the bank, Zepto creates the investigation, notifies your platform, and requests merchant action.

Warning

Make sure you submit evidence before the due date. Missing the deadline may result in the case being closed or rejected.

Success

Once accepted, the action request is completed and the dispute workflow progresses accordingly.

Important

Rejecting an action request without the correct review may cause avoidable operational issues.

Tip

Retrieve the investigation first, then inspect the active action request so you can present the right next step to your merchant.

via NPP

Scenario: Successful

The webhooks that are fired when you make a payment (from your primary account or the float account) are as follows:

  • payment.added
  • debit.scheduled
  • debtor_credit.scheduled
  • debit.maturing
  • debit.matured
  • debit.processing
  • debit.clearing
  • debit.cleared
  • debtor_credit.matured
  • debtor_credit.processing
  • debtor_credit.clearing
  • debtor_credit.cleared - (Funds were credited into the end customer's account)

For a successful NPP transaction, the final event that the system will fire is debtor_credit.cleared. Please note, that the above webhooks will be fired under the category payout


Scenario: Unsuccessful (with no channel switch to DE)

If you chose a standard Float account (with only NPP transactions or only DE), you would expect to receive the following webhooks:

  • payment.added
  • debit.scheduled
  • debtor_credit.scheduled
  • debit.maturing
  • debit.matured
  • debit.processing
  • debit.clearing
  • debit.cleared
  • debtor_credit.matured
  • debtor_credit.processing
  • debtor_credit.clearing
  • debtor_credit.returned - (Funds will be returned back to your account)

Overview

When a dispute is raised by the bank, Zepto creates the investigation, notifies your platform, and requests merchant action.

Warning

Make sure you submit evidence before the due date. Missing the deadline may result in the case being closed or rejected.

Success

Once accepted, the action request is completed and the dispute workflow progresses accordingly.

Important

Rejecting an action request without the correct review may cause avoidable operational issues.

Tip

Retrieve the investigation first, then inspect the active action request so you can present the right next step to your merchant.

  • credit.scheduled
  • credit.matured
  • credit.processing
  • credit.clearing
  • credit.cleared - (Funds have been returned to your account)
{
  "data": [
    {
      "ref": "C.2v404",
      "type": "credit",
      "amount": 103,
      "status": "cleared",
      "bank_ref": "CT.2ofh9",
      "category": "payout_reversal",
      "channels": [
        "float_account"
      ],
      "cleared_at": "2025-12-15T02:58:44Z",
      "created_at": "2025-12-15T02:58:43Z",
      "matures_at": "2025-12-15T02:58:43Z",
      "parent_ref": "PB.vhjt",
      "party_name": "Sujeet & Co.",
      "description": "Payout reversal of D.2mrc5 for Sujeet Shrestha due to Account closed",
      "party_bank_ref": "DT.61uw8",
      "party_nickname": "sujeets_au",
      "bank_account_id": "0197a14d-209f-7540-a059-22202fc8c031",
      "current_channel": "float_account",
      "party_contact_id": null,
      "reversal_details": {
        "source_debit_ref": "D.2mrc5",
        "source_credit_failure": {
          "code": "E103",
          "title": "Account Closed",
          "detail": "The target account is closed."
        },
        "source_credit_failure_reason": "account_closed"
      },
      "status_changed_at": "2025-12-15T02:58:44Z"
    }
  ],
  "event": {
    "at": "2025-12-15T02:58:44Z",
    "who": {
      "account_id": "2bdcc210-072d-4e09-b90e-757be5bd9853",
      "account_type": "Account",
      "bank_account_id": "0197a14d-209f-7540-a059-22202fc8c031",
      "bank_account_type": "BankAccount"
    },
    "type": "credit.cleared"
  }
}

So, in summary the key final state events are:

  • debtor_credit.cleared
  • debtor_credit.returned
  • credit.cleared - (category payout_reversal)

Scenario: Unsuccessful via NPP (but successfully processed via DE after channel switching)

If you chose an NPP hybrid account, failed NPP payments are retried via DE, you would expect to receive the following webhooks:

  • payment.added
  • debit.scheduled
  • debtor_credit.scheduled
  • debit.matured
  • debit.processing
  • debit.clearing
  • debit.cleared
  • debtor_credit.matured
  • debtor_credit.processing
  • debtor_credit.channel_switched - (Funds are being sent via the BECS channel)
  • debtor_credit.processing
  • debtor_credit.clearing
  • debtor_credit.cleared - (Funds have been sent to the end customer's bank and marked as cleared on the Zepto dashboard.)

Overview

When a dispute is raised by the bank, Zepto creates the investigation, notifies your platform, and requests merchant action.

Warning

Make sure you submit evidence before the due date. Missing the deadline may result in the case being closed or rejected.

Success

Once accepted, the action request is completed and the dispute workflow progresses accordingly.

Important

Rejecting an action request without the correct review may cause avoidable operational issues.

Tip

Retrieve the investigation first, then inspect the active action request so you can present the right next step to your merchant.


via Direct Entry (Direct Credit)

Scenario: Successful

The webhooks that are fired when you make a payment (from your primary account or the float account) are as follows:

  • payment.added
  • debit.scheduled
  • debtor_credit.scheduled
  • debit.maturing
  • debit.matured
  • debit.processing
  • debit.clearing
  • debit.cleared
  • debtor_credit.matured
  • debtor_credit.processing
  • debtor_credit.clearing
  • debtor_credit.cleared - (Funds were credited into the end customer's account)

Scenario: Unsuccessful

If you chose a standard Float account, you would expect to receive the following webhooks:

  • payment.added
  • debit.scheduled
  • debtor_credit.scheduled
  • debit.maturing
  • debit.matured
  • debit.processing
  • debit.clearing
  • debit.cleared
  • debtor_credit.matured
  • debtor_credit.processing
  • debtor_credit.clearing
  • debtor_credit.cleared
  • debtor_credit.returned - (Funds will be returned back to your account)

Overview

When a dispute is raised by the bank, Zepto creates the investigation, notifies your platform, and requests merchant action.

Warning

Make sure you submit evidence before the due date. Missing the deadline may result in the case being closed or rejected.

Success

Once accepted, the action request is completed and the dispute workflow progresses accordingly.

Important

Rejecting an action request without the correct review may cause avoidable operational issues.

Tip

Retrieve the investigation first, then inspect the active action request so you can present the right next step to your merchant.

  • credit.scheduled
  • credit.matured
  • credit.processing
  • credit.clearing
  • credit.cleared - (Funds have been returned to your account)

Visual flow


Did this page help you?