Submit a payout


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.

Endpoint destination URL
Click to copy

Request Parameters


This field contains additional data, which may be required for a particular request.


A container object for the payable amount information of the transaction.


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.


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.


An integer value that is added to the normal fraud score. The value can be either positive or negative.


The merchant account identifier you want to process the transaction request with.


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.


A container for the type of recurring contract to be retrieved.

The recurring.contract must be set to "PAYOUT".


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.


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.


The shopper's email address.


The shopper's name.

In case the entityType is Company, the shopperName.lastName must contain the company name.

This field is required to update the existing shopperName associated with a recurring contract.


The shopper's reference for the payout transaction.


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


The shopper's social security number.

Response parameters

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

    Show moreShow less
  • 400 - Bad Request

    A problem reading or understanding the request.

    Show moreShow less
  • 401 - Unauthorized

    Authentication required.

    Show moreShow less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show moreShow less
  • 422 - Unprocessable Entity

    A request validation error.

    Show moreShow less
  • 500 - Internal Server Error

    The server could not process the request.

    Show moreShow less