> 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/api-reference/payout-service/enroll-disburse-account.md).

# Enroll Disburse Account

## Overview

The `EnrollDisburseAccount` RPC 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                                               |
| -------------------- | ------------- | -------- | --------------------------------------------------------- |
| `merchant_payout_id` | string        | No       | Your internal identifier for the operation.               |
| `address`            | PayoutAddress | Yes      | Address information associated with the account.          |
| `payout_method_data` | 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.                |
| `access_token`       | SecretString  | No       | Access token for the connector, if required.              |

## Response Fields

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

## Example

```bash
grpcurl -H "x-connector: stripe" \
  -H "x-connector-config: {\"config\":{\"Stripe\":{\"api_key\":\"$STRIPE_API_KEY\"}}}" \
  -d '{
    "amount": {"minor_amount": 0, "currency": "USD"},
    "payout_method_data": {
      "ach": {
        "bank_account_number": "000123456789",
        "bank_routing_number": "110000000"
      }
    }
  }' \
  localhost:8080 types.PayoutService/EnrollDisburseAccount
```

```json
{
  "payout_status": "SUCCESS",
  "connector_payout_id": "ba_1Hh1XYZ2eZvKYlo2C",
  "status_code": 200
}
```

## Next Steps

* [Transfer Payout](/integrations/prism/api-reference/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.