> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/pay/advanced-features/payouts.md).

# Performing Payouts

A payout is a "proactive" transfer of funds from your merchant account to a customer's card, without the need for a previous transaction to occur. Payouts are often used for rewards, prize distribution, or other scenarios where you need to send money to a customer's card.

Keep in mind that a payout can only be made to a card that has been **previously used in your terminal** — there's no way to perform a payout to a completely new card.

If you're looking to return funds from a previous purchase, you should make a [refund](/pay/common-use-cases/refunds.md) instead.

## How to make a payout

Before you can make a payout, you'll need to handle two things:

1. **Get a credit password**. You'll need to pass this as the `zPass` parameter in your request. To get one, reach out to Hyp support by phone (\*6488, extension 3) or via [WhatsApp](https://wa.me/972732345000). This multiple-use password will be sent to the mobile number registered to the terminal owner's account.
2. [**Get a card token**](/pay/common-use-cases/tokenization.md). You'll need a token for the card you want to make a payout to. Make sure you save both the token (`Token`) and the card's expiration date (`Tokef`).

Once you've got those ready, make a GET request to `https://pay.hyp.co.il/p/` that looks something like this:

{% code overflow="wrap" %}

```http
https://pay.hyp.co.il/p/?action=soft&Masof=0010345518&PassP=your-api-password&zPass=8179&Amount=10&CC=4724478937284730772&Tmonth=05&Tyear=31&Token=True&UserId=203269535&ClientName=Jenny&Info=payout
```

{% endcode %}

The request includes these parameters:

* `action`: Set this to `soft`.
* `Masof`: Your terminal number.
* `PassP`: Your API password.
* `zPass`: Your credit password.
* `Amount`: The amount to be credited to the customer. This should be a positive number, just like in a regular charge. The system knows to treat it as a credit because of the `zPass` parameter.
* `CC`: The card token you previously saved as `Token`.
* `Tmonth`: The card's expiration month. Use the two-digit month part from `Tokef`.
* `Tyear`: The card's expiration year. Use the two-digit year part from `Tokef`.
* `Token`: Set this to `True` to indicate that the request uses a card token.
* `UserId`: The customer's Israeli ID number. If you're making a payout to a non-Israeli card or you don't want to save the ID number, set this to `000000000`.
* `ClientName`: The customer's name.
* `Info`: Any extra info you want to include with the transaction.

Here's an example of a successful payout response:

```
Id=5920751&CCode=0&Amount=100&ACode=0034903&Fild1=&Fild2=&Fild3=&Hesh=47
```

In the response, `CCode=0` means the payout was successful. If there's an issue, you'll receive a different [status code](/pay/reference/response-status-codes.md) indicating the error.

The `Id` is the unique transaction ID for the payout.


---

# 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://developers.hyp.co.il/pay/advanced-features/payouts.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.