# Create out payment

Get your strong authentication RSA private key from Easypay Backoffice on menu:Web Services->Configuration API 2.0->Keys.

Endpoint: POST /out_payment
Version: 2.0
Security: accountId, apiKey, signatureAuth

## Request fields (application/json):

  - `customer` (object, required)
    The Customer object contains the necessary details about the customer involved in the transaction. This includes identification information, contact details, and preferences. All fields are optional unless specified otherwise.

  - `customer.id` (string)
    Unique identifier for the customer. When provided, it links the transaction to an existing customer record.
    Example: "649e88cf-0b78-4c36-8f99-33f5ebb812a1"

  - `customer.name` (string)
    Full name of the customer. This is typically displayed on receipts and statements.
    Example: "John Doe"

  - `customer.email` (string)
    Customer's email address. Used for sending receipts, notifications, and payment confirmations.
    Example: "john.doe@example.com"

  - `customer.phone` (string)
    The contact phone number of the customer, excluding the country code indicator (e.g., "+351"). This field is used for communication purposes. If the payment method is MBWAY, the phone_number is required and is used to send the MBWAY push notification.
    Example: "911234567"

  - `customer.phone_indicative` (string)
    The country code indicator for the customer's phone number (e.g., "351" for Portugal). This field is used in conjunction with the phone number to ensure proper international dialing and communication.
    Example: "+351"

  - `customer.fiscal_number` (string)
    Customer's tax identification number or fiscal number. Format may vary by country.
    Example: "PT123456789"

  - `customer.key` (string)
    A customizable text field for users to input their own identifier for the customer. This can be any string that helps the user uniquely identify the customer in their own system.
    Example: "customer Key Example"

  - `customer.language` (string)
    Preferred language for customer communications. Uses ISO 639-1 language codes.
    Enum: "PT", "EN", "ES"

  - `key` (string)
    Merchant identification key

  - `value` (number, required)
    Value will be rounded to 2 decimals

  - `type` (string)
    Optional - only applicable to method transfer
    Enum: "normal", "instant"

  - `schedule_at` (string)
    Schedule date to execute the payment

  - `descriptive` (string)
    Description for the out payment.

  - `account` (object)

  - `account.id` (string)

  - `out_account` (object, required)

  - `out_account.account_holder` (string, required)
    Bank account holder name

  - `out_account.iban` (string, required)
    Only IBANS from SEPA zones are supported

  - `out_account.email` (string, required)

  - `out_account.phone` (string, required)

  - `out_account.key` (string)
    Custom string controlled by our clients

  - `out_account.country_code` (string)
    Bank account country code

  - `method` (string, required)
    Enum: "transfer", "mb"

  - `timestamp` (string, required)
    Unix timestamp UTC, must be no more than 1 minute before or after real time, if not the strong authentication signature will not be valid

## Response 201 fields (application/json):

  - `status` (string)
    Example: "ok"

  - `message` (array)
    Example: ["Your request was successfully created"]

  - `id` (string)
    A unique identifier for the resource. While typically formatted as a UUID (Universally Unique Identifier), it can also be in other formats as defined by the user. This field ensures the resource can be distinctly recognized and referenced.

  - `method` (object)

  - `method.type` (string)
    Enum: "normal", "instant"

  - `customer` (object)
    Customer associated with the out payment.

  - `customer.id` (string)
    Unique identifier for the customer.

  - `out_account` (object)
    Destination SEPA bank account for the out payment.

  - `out_account.id` (string)
    Unique identifier for the destination account.

## Response 400 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.