---
title: "POST /find_disbursements"
method: POST
path: "/find_disbursements"
tags: ["Payments"]
---

# POST /find_disbursements

`POST /find_disbursements`

A dedicated endpoint for retrieving disbursement (i.e., push) payment history. This endpoint allows clients to retrieve a list of disbursements for specific push orders (<code>pnm_order_identifier</code> or <code>site_order_identifier</code>) or the push orders associated with a specific customer (<code>pnm_customer_identifier</code> or <code>site_customer_identifier</code>). This endpoint is only for returning push payments and not regular consumer payments (use the [/find_payments](https://apidocs.paynearme.com/devdocs/reference/post_find-payments) endpoint for regular consumer payments).

## Request body

- union — Retrieves disbursement (push payment) history for a specified push order or customer.
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `pnm_order_identifier` string, required — The PayNearMe-created ID for the push order.
    - `site_order_identifier` string — The arbitrary string that the client uses to refer to the push order.
    - `pnm_customer_identifier` string — A PayNearMe-assigned ID for the customer.
    - `site_customer_identifier` string — A unique, client-defined ID for the consumer.
    - `sort` 'asc' | 'desc' — Sort direction: 'asc' (oldest first) or 'desc' (newest first). Default: 'desc'
    - `limit` integer — Used for pagination, this parameter specifies the maximum number of disbursements to return. Default value is <code>10</code>.
    - `offset` integer — Used for pagination, this parameter specifies the number of disbursement payments to skip within the response. Default value is <code>0</code>.
    - `start_date` string, date — Filter on or after this date (YYYY-MM-DD)
    - `end_date` string, date — Filter on or before this date (YYYY-MM-DD)
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `pnm_order_identifier` string — The PayNearMe-created ID for the push order.
    - `site_order_identifier` string, required — The arbitrary string that the client uses to refer to the push order.
    - `pnm_customer_identifier` string — A PayNearMe-assigned ID for the customer.
    - `site_customer_identifier` string — A unique, client-defined ID for the consumer.
    - `sort` 'asc' | 'desc' — Sort direction: 'asc' (oldest first) or 'desc' (newest first). Default: 'desc'
    - `limit` integer — Used for pagination, this parameter specifies the maximum number of disbursements to return. Default value is <code>10</code>.
    - `offset` integer — Used for pagination, this parameter specifies the number of disbursement payments to skip within the response. Default value is <code>0</code>.
    - `start_date` string, date — Filter on or after this date (YYYY-MM-DD)
    - `end_date` string, date — Filter on or before this date (YYYY-MM-DD)
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `pnm_order_identifier` string — The PayNearMe-created ID for the push order.
    - `site_order_identifier` string — The arbitrary string that the client uses to refer to the push order.
    - `pnm_customer_identifier` string, required — A PayNearMe-assigned ID for the customer.
    - `site_customer_identifier` string — A unique, client-defined ID for the consumer.
    - `sort` 'asc' | 'desc' — Sort direction: 'asc' (oldest first) or 'desc' (newest first). Default: 'desc'
    - `limit` integer — Used for pagination, this parameter specifies the maximum number of disbursements to return. Default value is <code>10</code>.
    - `offset` integer — Used for pagination, this parameter specifies the number of disbursement payments to skip within the response. Default value is <code>0</code>.
    - `start_date` string, date — Filter on or after this date (YYYY-MM-DD)
    - `end_date` string, date — Filter on or before this date (YYYY-MM-DD)
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `pnm_order_identifier` string — The PayNearMe-created ID for the push order.
    - `site_order_identifier` string — The arbitrary string that the client uses to refer to the push order.
    - `pnm_customer_identifier` string — A PayNearMe-assigned ID for the customer.
    - `site_customer_identifier` string, required — A unique, client-defined ID for the consumer.
    - `sort` 'asc' | 'desc' — Sort direction: 'asc' (oldest first) or 'desc' (newest first). Default: 'desc'
    - `limit` integer — Used for pagination, this parameter specifies the maximum number of disbursements to return. Default value is <code>10</code>.
    - `offset` integer — Used for pagination, this parameter specifies the number of disbursement payments to skip within the response. Default value is <code>0</code>.
    - `start_date` string, date — Filter on or after this date (YYYY-MM-DD)
    - `end_date` string, date — Filter on or before this date (YYYY-MM-DD)

## Response `201`

Disbursements Found

- FindDisbursementsResponse — Response to the <code>/find_disbursements</code> call, which contains a list of disbursement (push) payments matching the search request's criteria. Each disbursement includes full payment details with order and customer identifiers for cross-referencing.
  - `status` string — Response status (e.g., 'ok')
  - `disbursements` FindDisbursementsPayment — Disbursement payment (push) object returned by the `/find_disbursements` endpoint. The `payment_type` values include `paypal_push`, `venmo_push`, `ach_push`, or `push-debit`.
    - `payment_made` string, date-time — The date and time when the customer made the payment.
    - `payment_amount` number — The total amount of the payment including convenience fees.
    - `payment_currency` string — USD
    - `payment_status` 'approved' | 'authorized' | 'canceled' | 'refunded' | 'rejected' | 'waiting for review' — The status of the payment.
    - `payment_type` 'ach' | 'ach_push' | 'cash' | 'cash_app' | 'credit' | 'debit' | 'paypal' | 'paypal-push' | 'pin4' | 'push-debit' | 'venmo' | 'venmo-push' — The type of payment method used for the transaction. Payment methods prefixed or suffixed with <code>push</code> are for disbursement transactions.
    - `payment_account` string — A short description of the payment method.
    - `payment_method_identifier` string — A unique ID for the payment method.
    - `net_payment_amount` number — The payment amount that is settled to the consumer after all client, retailer (if applicable), and PayNearMe fees have been taken out.
    - `net_payment_currency` string — USD
    - `payment_processing_fee` number — The fee amount charged for processing the transaction.
    - `payment_processing_fee_currency` string — USD
    - `pnm_processing_fee` number — The fee amount that PayNearMe charges for processing the transaction.
    - `pnm_processing_fee_currency` string — USD
    - `settled_to_site` string — If set to <code>true</code>, the payment has been settled to the client's account.
    - `date_settled_to_merchant` string, date — The date in <i>YYYY-MM-DD</i> format when the payment was settled to the client.
    - `pnm_payment_identifier` string — A unique string identifier for the payment.
    - `retailer_identifier` string — A unique PayNearMe-assigned ID for a retailer.
    - `pricing_schedule_name` string — Specifies the name of the pricing schedule (e.g.,<code>agent</code>, <code>agent_recurring</code>, <code>consumer</code>, <code>consumer_recurring</code>,<code>consumer_ivr</code>). Supported values can include site-configured pricing schedules.
    - `site_channel` 'agent' | 'agent_waived' | 'consumer' | 'consumer_ivr' | 'kiosk' | 'agent_recurring' | 'consumer_recurring' — The payment channel where this payment was created.
    - `payment_receipt_text` string — Custom text that can be returned in the authorization callback response. Up to 75 lines of 40 character each can be included.
    - `site_order_identifier` string — The client-defined identifier for the order associated with this disbursement.
    - `pnm_order_identifier` string — The PayNearMe-created identifier for the order associated with this disbursement.
    - `site_customer_identifier` string — The client-defined identifier for the customer associated with this disbursement.
    - `pnm_customer_identifier` string — The PayNearMe-created identifier for the customer associated with this disbursement.
    - `merchant_settlements` MerchantSettlements — The Merchant Settlements object indicates where and for how much a payment was settled.
      - `settlement_method_identifier` string — A unique, PayNearMe-provided ID for the settlement.
      - `settlement_type` 'net_payment' | 'gross_payment' — Indicates whether the settlment is a <code>net_payment</code> or a <code>gross_payment</code>.
      - `settlement_amount` number — The amount to be settled
      - `settlement_currency` string — USD
    - `refund` Refund — The Refund object indicates the status of the payment refund.
      - `refund_status` 'started' | 'completed' — The status of the refund. Supported options include <code>started</code> and <code>completed</code>.
      - `refund_amount` string — The amount to be refunded.
      - `refund_currency` string — USD
      - `unsettle_to_merchant_amount` string — The amount that will be unsettled from the client account (i.e., the payment amount less the convenience fee)
      - `unsettle_to_merchant_currency` string — USD
      - `unsettled_from_collector_amount` string — The amount that will be unsettled from the collector (if applicable).

---

[API](https://skmtc.net/paynearme/apis/paynearme-api-v3-0.md) · [All operations](https://skmtc.net/paynearme/apis/paynearme-api-v3-0/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paynearme/paynearme-api-v3-0/revisions/44cba4f8b80f/schema)
