> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/payout-service/5.-to-the-account.md).

# 5. To the account

## To the account

<mark style="color:green;">`POST`</mark> `{{Base Address}}/api/paywall/payout/send/account`

Simply send a request to the provided address: POST {{Base Address}}/api/paywall/payout/send/iban. You can use the appropriate 'Base Address' for both the testing and production environments as

{% hint style="info" %}
**Important**: In order to use the Payout - Account service, you need to send the '**apikeyprivate**' and '**apiclientprivate**' parameters in the 'Header' field.

[<mark style="color:green;">**PaymentAPI Address**</mark>](/payment-orchestration-integration-document/environment.md)
{% endhint %}

<table><thead><tr><th width="174">Parameter</th><th width="106.33333333333331">Type</th><th width="145">Compulsory</th><th>Description</th></tr></thead><tbody><tr><td>apikeyprivate</td><td>string</td><td>Yes</td><td>The Private Key obtained from the merchant panel.</td></tr><tr><td>apiclientprivate</td><td>string</td><td>Yes</td><td>The Private Client obtained from the merchant panel.</td></tr></tbody></table>

**The parameters that need to be sent to the service are as follows:**

<table><thead><tr><th width="228">Parameter</th><th width="106">Type</th><th width="175">Compulsory</th><th>Description</th></tr></thead><tbody><tr><td>PayoutProviderKey</td><td>string</td><td>Yes</td><td>The key term for the PayOut provider in Paywall</td></tr><tr><td>MerchantGroupCode</td><td>string</td><td>Yes</td><td>This is the group code you will define for tracking the PayOut transaction. With the relevant code, you can assign the same group code to your transfers under a specific transaction and report them.</td></tr><tr><td>MerchantUniqueCode</td><td>string</td><td>Yes</td><td>The unique code you will define for tracking the PayOut transaction (you cannot use the same codes within the same month).</td></tr><tr><td>ReceiverTitle</td><td>string</td><td>Yes</td><td>Recipient name or company name</td></tr><tr><td>ReceiverAccount</td><td>string</td><td>Yes</td><td>Recipient Account</td></tr><tr><td>ReceiverIdentity</td><td>string</td><td>Yes/No</td><td>Recipient identification information (TCKN - Turkish Citizen ID or VKN - Tax Identification Number)</td></tr><tr><td>Description</td><td>string</td><td>Yes</td><td>Description to be communicated to the recipient for PayOut.</td></tr><tr><td>Amount</td><td>decimal</td><td>Yes</td><td>PayOut amount</td></tr><tr><td>CurrencyId</td><td>int</td><td>Yes</td><td>Currency<br><br>Bkz: <a href="/pages/bahfUMz1dqpN1ZCnpVtM">Currency</a></td></tr><tr><td>CallbackSupport</td><td>bool</td><td>No</td><td>Should feedback be provided in case of asynchronous failure or refund of the PayOut transaction?</td></tr><tr><td>CallbackAddress</td><td>string</td><td>Yes (Conditional)</td><td>Address to which feedback will be sent</td></tr></tbody></table>

{% tabs %}
{% tab title="JSON" %}
{% code overflow="wrap" lineNumbers="true" %}

```json5
{
    "PayoutProviderKey": "ProviderKey",
    "MerchantUniqueCode": "ASDJHISOFIFJDJAJF23423",
    "ReceiverTitle": "Receiver Title",
    "ReceiverAccount": "1234567890",
    "ReceiverIdentity": "11111111110",
    "Description": "Description",
    "Amount": 10,
    "CurrencyId": 1
}
```

{% endcode %}
{% endtab %}

{% tab title="C#" %}

```csharp
// Soon
```

{% endtab %}

{% tab title="GO" %}

```go
// Soon
```

{% endtab %}

{% tab title="Java" %}

```java
// Soon
```

{% endtab %}

{% tab title="PHP" %}

```php
// Soon
```

{% endtab %}

{% tab title="Python" %}

```python
// Soon
```

{% endtab %}

{% tab title="Ruby" %}

```ruby
// Soon
```

{% endtab %}

{% tab title="TypeScript" %}

```typescript
// Soon
```

{% endtab %}

{% tab title="Curl" %}

```sh
// Soon
```

{% endtab %}
{% endtabs %}

**Response returned from the service:**

<table><thead><tr><th width="156">Parameter</th><th width="91.33333333333331">Type</th><th>Description</th></tr></thead><tbody><tr><td>Body</td><td>object</td><td>Optional JSON containing details about the payment.</td></tr><tr><td>ErrorCode</td><td>int</td><td>Error code. Returns '0' if the transaction is successful.</td></tr><tr><td>Result</td><td>bool</td><td>Returns a value of 'true' or 'false'. Returns 'true' if the transaction is successful.</td></tr><tr><td>Message</td><td>string</td><td>If the transaction fails, this is the message specified for the error, providing language support according to the locale parameter.</td></tr></tbody></table>

{% tabs %}
{% tab title="JSON" %}
{% code overflow="wrap" lineNumbers="true" %}

```json5
{
    "ErrorCodeType": 1,
    "ErrorMessage": null,
    "ErrorCode": 0,
    "Result": true,
    "Message": "",
    "Body": {
        "Result": true,
        "PayoutTransactionId": 1368323410,
        "MerchantUniqueCode": "e429eb20-d743-4527-a3f9-a92eba2becb0",
        "UniqueCode": "85471308-d388-4fd3-88b5-f709f97f7a16",
        "Amount": 1412341322.64,
        "Error": {
            "ProviderErrorCode": "",
            "ProviderErrorMessage": ""
        }
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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://developer.paywall.one/payment-orchestration-integration-document/payout-service/5.-to-the-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.