---
title: "Submit a payout"
method: POST
path: "/submitThirdParty"
tags: ["Initialization"]
---

# Submit a payout

`POST /submitThirdParty`

> This endpoint is **deprecated** and no longer supports new integrations. Do one of the following:
>- If you are building a new integration, use the POST [/transfers](https://docs.adyen.com/api-explorer/transfers/latest/post/transfers) endpoint instead.
> - If you are already using the Payout API, reach out to your Adyen contact to learn how to migrate to the Transfers API.
>
> With the Transfers API, you can:
> - Handle multiple payout use cases with a single API.
> - Use new payout functionalities, such as instant payouts to bank accounts.
> - Receive webhooks with more details and defined transfer states.
>
> For more information about the payout features of the Transfers API, see our [Payouts](https://docs.adyen.com/payouts/payout-service) documentation.


Submits a payout using the previously stored payment details. To store payment details, use the `/storeDetail` API call.

The submitted payout must be confirmed or declined either by a reviewer or via `/confirmThirdParty` or `/declineThirdParty` calls.

## Request body

- SubmitRequest
  - `additionalData` object — This field contains additional data, which may be required for a particular request.
  - `amount` Amount, required
    - `currency` string, required — The three-character [ISO currency code](https://docs.adyen.com/development-resources/currency-codes#currency-codes) of the amount.
    - `value` integer, required — The numeric value of the amount, in [minor units](https://docs.adyen.com/development-resources/currency-codes#minor-units).
  - `dateOfBirth` string, date — The date of birth. Format: ISO-8601; example: YYYY-MM-DD For Paysafecard it must be the same as used when registering the Paysafecard account. > This field is mandatory for natural persons. > This field is required to update the existing `dateOfBirth` that is associated with this recurring contract.
  - `entityType` 'NaturalPerson' | 'Company' — The type of the entity the payout is processed for. Allowed values: * NaturalPerson * Company > This field is required to update the existing `entityType` that is associated with this recurring contract.
  - `fraudOffset` integer — An integer value that is added to the normal fraud score. The value can be either positive or negative.
  - `merchantAccount` string, required — The merchant account identifier you want to process the transaction request with.
  - `nationality` string — The shopper's nationality. A valid value is an ISO 2-character country code (e.g. 'NL'). > This field is required to update the existing nationality that is associated with this recurring contract.
  - `recurring` Recurring, required
    - `contract` 'ONECLICK' | 'ONECLICK,RECURRING' | 'RECURRING' | 'PAYOUT' | 'EXTERNAL' — The type of recurring contract to be used. Possible values: * `ONECLICK` – Payment details can be used to initiate a one-click payment, where the shopper enters the [card security code (CVC/CVV)](https://docs.adyen.com/payments-fundamentals/payment-glossary#card-security-code-cvc-cvv-cid). * `RECURRING` – Payment details can be used without the card security code to initiate [card-not-present transactions](https://docs.adyen.com/payments-fundamentals/payment-glossary#card-not-present-cnp). * `ONECLICK,RECURRING` – Payment details can be used regardless of whether the shopper is on your site or not. * `PAYOUT` – Payment details can be used to [make a payout](https://docs.adyen.com/online-payments/online-payouts). * `EXTERNAL` - Use this when you store payment details and send the raw card number or network token directly in your API request.
    - `recurringDetailName` string — A descriptive name for this detail.
    - `tokenService` 'VISATOKENSERVICE' | 'MCTOKENSERVICE' | 'AMEXTOKENSERVICE' | 'TOKEN_SHARING' — The name of the token service.
  - `reference` string, required — The merchant reference for this payout. This reference will be used in all communication to the merchant about the status of the payout. Although it is a good idea to make sure it is unique, this is not a requirement.
  - `selectedRecurringDetailReference` string, required — This is the `recurringDetailReference` you want to use for this payout. You can use the value LATEST to select the most recently used recurring detail.
  - `shopperEmail` string, required — The shopper's email address.
  - `shopperName` Name
    - `firstName` string, required — The first name.
    - `lastName` string, required — The last name.
  - `shopperReference` string, required — The shopper's reference for the payout transaction.
  - `shopperStatement` string — The description of this payout. This description is shown on the bank statement of the shopper (if this is supported by the chosen payment method).
  - `socialSecurityNumber` string — The shopper's social security number.

## Response `200`

OK - the request has succeeded.

- SubmitResponse
  - `additionalData` object — This field contains additional data, which may be returned in a particular response.
  - `pspReference` string, required — A new reference to uniquely identify this request.
  - `refusalReason` string — In case of refusal, an informational message for the reason.
  - `resultCode` string, required — The response: * In case of success, it is `payout-submit-received`. * In case of an error, an informational message is returned.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

---

[API](https://skmtc.net/adyen/apis/payoutservice.md) · [All operations](https://skmtc.net/adyen/apis/payoutservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/payoutservice/versions/a2c38f8801fa/schema)