> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/prism/node/payout-service/enroll-disburse-account.md).

# Enroll Disburse Account

## Overview

The `enrollDisburseAccount` method registers and verifies a destination account (like a bank account) to receive disbursements from your platform.

## Purpose

Use this operation to securely enroll payout destinations.

| Scenario                     | Developer Implementation                              |
| ---------------------------- | ----------------------------------------------------- |
| Link a vendor's bank account | Call `enrollDisburseAccount` with their bank details. |

## Request Fields

| Field              | Type          | Required | Description                                               |
| ------------------ | ------------- | -------- | --------------------------------------------------------- |
| `merchantPayoutId` | string        | No       | Your internal identifier for the operation.               |
| `address`          | PayoutAddress | Yes      | Address information associated with the account.          |
| `payoutMethodData` | PayoutMethod  | No       | Specific details of the payout instrument being enrolled. |
| `amount`           | Money         | Yes      | The amount to be paid out (if enrolling inline).          |
| `customer`         | Customer      | No       | Details about the customer/account holder.                |
| `accessToken`      | SecretString  | No       | Access token for the connector, if required.              |

## Response Fields

| Field               | Type                     | Required | Description                                       |
| ------------------- | ------------------------ | -------- | ------------------------------------------------- |
| `merchantPayoutId`  | string                   | No       | Your internal identifier.                         |
| `payoutStatus`      | PayoutEnums.PayoutStatus | No       | The status of the enrollment.                     |
| `connectorPayoutId` | string                   | No       | The unique identifier assigned by the connector.  |
| `error`             | ErrorInfo                | No       | Details of any error that occurred.               |
| `statusCode`        | uint32                   | Yes      | The HTTP status code returned from the connector. |

## Example

### SDK Setup

```javascript
const { PayoutClient } = require('hyperswitch-prism');

const payoutClient = new PayoutClient({
    connector: 'stripe',
    apiKey: '[REDACTED_ENV_SECRET]',
    environment: 'SANDBOX'
});
```

### Request

```javascript
const request = {
    amount: {
        minorAmount: 0,
        currency: "USD"
    },
    payoutMethodData: {
        ach: {
            bankAccountNumber: "000123456789",
            bankRoutingNumber: "110000000"
        }
    }
};

const response = await payoutClient.enrollDisburseAccount(request);
```

### Response

```javascript
{
    payoutStatus: "SUCCESS",
    connectorPayoutId: "ba_1Hh1XYZ2eZvKYlo2C",
    statusCode: 200
}
```

## Next Steps

* [Transfer Payout](/integrations/prism/node/payout-service/transfer.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/prism/node/payout-service/enroll-disburse-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.