> 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/java/payout-service/stage.md).

# Stage

## Overview

The `stage` method allows you to prepare or stage a payout before it is executed. This can be used in workflows where payouts are reviewed or batched before final transfer.

## Purpose

Use this operation to put a payout into a staged state.

| Scenario                    | Developer Implementation                        |
| --------------------------- | ----------------------------------------------- |
| Prepare a payout for review | Call `stage` with the quote details and amount. |

## Request Fields

| Field                 | Type               | Required | Description                                        |
| --------------------- | ------------------ | -------- | -------------------------------------------------- |
| `merchantQuoteId`     | string             | No       | Your internal quote identifier.                    |
| `address`             | PayoutAddress      | Yes      | Address information associated with the payout.    |
| `amount`              | Money              | Yes      | The amount to be staged.                           |
| `destinationCurrency` | Currency           | Yes      | The currency in which the payout will be received. |
| `customer`            | Customer           | No       | Details about the customer.                        |
| `browserInfo`         | BrowserInformation | No       | Information about the user's browser.              |
| `accessToken`         | SecretString       | No       | Access token for the connector, if required.       |

## Response Fields

| Field               | Type                     | Required | Description                                              |
| ------------------- | ------------------------ | -------- | -------------------------------------------------------- |
| `merchantPayoutId`  | string                   | No       | Your internal identifier passed to the payout processor. |
| `payoutStatus`      | PayoutEnums.PayoutStatus | No       | The current status of the staged payout.                 |
| `connectorPayoutId` | string                   | No       | The unique payout ID 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

```java
import com.hyperswitch.prism.PayoutClient;
import java.util.Map;
import java.util.HashMap;

PayoutClient payoutClient = PayoutClient.builder()
    .connector("stripe")
    .apiKey("YOUR_API_KEY")
    .environment("SANDBOX")
    .build();
```

### Request

```java
Map<String, Object> request = new HashMap<>();
request.put("merchantQuoteId", "quote_123");
request.put("amount", Map.of("minorAmount", 1000, "currency", "USD"));
request.put("destinationCurrency", "USD");

Response response = payoutClient.stage(request);
```

### Response

```java
{
    "payoutStatus": "PENDING",
    "connectorPayoutId": "po_1Hh1XYZ2eZvKYlo2C",
    "statusCode": 200
}
```

## Next Steps

* [Transfer Payout](/integrations/prism/java/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/java/payout-service/stage.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.