---
title: "Store payout details"
method: POST
path: "/storeDetail"
tags: ["Initialization"]
---

# Store payout details

`POST /storeDetail`

> This endpoint is **deprecated** and no longer supports new integrations. Do one of the following:
>- If you are building a new integration, use the [Transfers API](https://docs.adyen.com/api-explorer/transfers/latest/overview) 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.


Stores payment details under the `PAYOUT` recurring contract. These payment details can be used later to submit a payout via the `/submitThirdParty` call.

## Request body

- StoreDetailRequest
  - `additionalData` object — This field contains additional data, which may be required for a particular request.
  - `bank` BankAccount
    - `bankAccountNumber` string — The bank account number (without separators).
    - `bankCity` string — The bank city.
    - `bankLocationId` string — The location id of the bank. The field value is `nil` in most cases.
    - `bankName` string — The name of the bank.
    - `bic` string — The [Business Identifier Code](https://en.wikipedia.org/wiki/ISO_9362) (BIC) is the SWIFT address assigned to a bank. The field value is `nil` in most cases.
    - `countryCode` string — Country code where the bank is located. A valid value is an ISO two-character country code (e.g. 'NL').
    - `iban` string — The [International Bank Account Number](https://en.wikipedia.org/wiki/International_Bank_Account_Number) (IBAN).
    - `ownerName` string — The name of the bank account holder. If you submit a name with non-Latin characters, we automatically replace some of them with corresponding Latin characters to meet the FATF recommendations. For example: * χ12 is converted to ch12. * üA is converted to euA. * Peter Møller is converted to Peter Mller, because banks don't accept 'ø'. After replacement, the ownerName must have at least three alphanumeric characters (A-Z, a-z, 0-9), and at least one of them must be a valid Latin character (A-Z, a-z). For example: * John17 - allowed. * J17 - allowed. * 171 - not allowed. * John-7 - allowed. > If provided details don't match the required format, the response returns the error message: 203 'Invalid bank account holder name'.
    - `taxId` string — The bank account holder's tax ID.
  - `billingAddress` Address
    - `city` string, required — The name of the city. Maximum length: 3000 characters.
    - `country` string, required — The two-character ISO-3166-1 alpha-2 country code. For example, **US**. > If you don't know the country or are not collecting the country from the shopper, provide `country` as `ZZ`.
    - `houseNumberOrName` string, required — The number or name of the house. Maximum length: 3000 characters.
    - `postalCode` string, required — A maximum of five digits for an address in the US, or a maximum of ten characters for an address in all other countries.
    - `stateOrProvince` string — The two-character ISO 3166-2 state or province code. For example, **CA** in the US or **ON** in Canada. > Required for the US and Canada.
    - `street` string, required — The name of the street. Maximum length: 3000 characters. > The house number should not be included in this field; it should be separately provided via `houseNumberOrName`.
  - `card` Card
    - `cvc` string — The [card verification code](https://docs.adyen.com/payments-fundamentals/payment-glossary#card-security-code-cvc-cvv-cid) (1-20 characters). Depending on the card brand, it is known also as: * CVV2/CVC2 – length: 3 digits * CID – length: 4 digits > If you are using [Client-Side Encryption](https://docs.adyen.com/classic-integration/cse-integration-ecommerce), the CVC code is present in the encrypted data. You must never post the card details to the server. > This field must be always present in a [one-click payment request](https://docs.adyen.com/classic-integration/recurring-payments). > When this value is returned in a response, it is always empty because it is not stored.
    - `expiryMonth` string — The card expiry month. Format: 2 digits, zero-padded for single digits. For example: * 03 = March * 11 = November
    - `expiryYear` string — The card expiry year. Format: 4 digits. For example: 2020
    - `holderName` string — The name of the cardholder, as printed on the card.
    - `issueNumber` string — The issue number of the card (for some UK debit cards only).
    - `number` string — The card number (4-19 characters). Do not use any separators. When this value is returned in a response, only the last 4 digits of the card number are returned.
    - `startMonth` string — The month component of the start date (for some UK debit cards only).
    - `startYear` string — The year component of the start date (for some UK debit cards only).
  - `dateOfBirth` string, date, required — The date of birth. Format: [ISO-8601](https://www.w3.org/TR/NOTE-datetime); 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.
  - `entityType` 'NaturalPerson' | 'Company', required — The type of the entity the payout is processed for.
  - `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, with which you want to process the transaction.
  - `nationality` string, required — The shopper's nationality. A valid value is an ISO 2-character country code (e.g. 'NL').
  - `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.
  - `selectedBrand` string — The name of the brand to make a payout to. For Paysafecard it must be set to `paysafecard`.
  - `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 payment transaction.
  - `socialSecurityNumber` string — The shopper's social security number.

## Response `200`

OK - the request has succeeded.

- StoreDetailResponse
  - `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.
  - `recurringDetailReference` string, required — The token which you can use later on for submitting the payout.
  - `resultCode` string, required — The result code of the transaction. `Success` indicates that the details were stored successfully.

## 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)