# Update a single Payment

Apply partial modifications to a single payment resource.

Endpoint: PATCH /single/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Request fields (application/json):

  - `currency` (string)
    ISO 4217 currency code. If not specified, the default currency is set to EUR.
    Example: "EUR"

  - `customer` (object)
    The Customer object contains detailed information about the customer involved in the transaction. Used for update operations where all fields are optional.

  - `customer.name` (string)
    The full name of the customer. This field is used to identify the customer and personalize interactions.
    Example: "Jonh Doe"

  - `customer.email` (string)
    The email address of the customer. Used for communication purposes, including sending transaction confirmations and receipts.
    Example: "customer@example.com"

  - `customer.phone` (string)
    The contact phone number of the customer, excluding the country code indicator. Used for communication purposes.
    Example: "962496235"

  - `customer.phone_indicative` (string)
    The country code indicator for the customer's phone number (e.g., "351" for Portugal).
    Example: "351"

  - `customer.fiscal_number` (string)
    The customer's fiscal number (prefixed by the country code).
    Example: "PT277712580"

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

  - `customer.language` (string)
    The language preference of the customer, specified in the ISO 639-1 Alpha-2 format (e.g., "EN" for English, "PT" for Portuguese).
    Example: "PT"

  - `sdd_mandate` (object)
    The SDD Mandate object contains the necessary fields to update a SEPA Direct Debit mandate. All fields are optional for update operations.

  - `sdd_mandate.iban` (string)
    The International Bank Account Number (IBAN) of the debtor's account. This field is used to uniquely identify the debtor's bank account across international borders, ensuring accurate and efficient processing of SEPA Direct Debit transactions. The IBAN is a standardized format that includes the country code, check digits, bank code, and account number.
    Example: "PT50002700000001234567833"

  - `sdd_mandate.key` (string)
    A customizable text field for users to input their own identifier for the SDD mandate.
    Example: "Sdd mandate Key Example"

  - `sdd_mandate.name` (string)
    Full name of the account holder as it appears on the bank account.
    Example: "John Doe"

  - `sdd_mandate.email` (string)
    Email address of the account holder for mandate-related communications.
    Example: "john.doe@example.com"

  - `sdd_mandate.phone` (string)
    Phone number of the account holder without country code.
    Example: "911234567"

  - `sdd_mandate.account_holder` (string)
    The name of the person or entity that holds the bank account. This field is used to identify the owner of the bank account involved in the transaction, ensuring that the correct account is credited or debited.
    Example: "John Doe"

  - `expiration_time` (string)

## Response 200 fields (application/json):

  - `id` (string)

  - `message` (array)
    An array of messages providing details about the response status. These messages give additional context about the operation result.

  - `status` (string)
    Indicates the overall status of the API response. 'ok' means the request was successful, 'error' indicates there was a problem.
    Enum: "ok", "error"

  - `method` (object)

  - `method.type` (any)
    Enum: "CC", "DD", "VI", "MBW", "MB", "AP", "GP", "SW"

  - `method.status` (any)
    Enum: "active", "deleted", "pending"

  - `method.entity` (string)
    The identifier for the Multibanco entity to which the payment should be routed. This field specifies the entity code required for processing the payment through the Multibanco network, ensuring that the payment is directed to the correct recipient.
    Example: "11683"

  - `method.reference` (string)
    The unique payment reference number issued for the specific Multibanco entity. This field is used by the end user to make a payment at an ATM or through home banking. It ensures that the payment is correctly attributed to the intended transaction and recipient.
    Example: "665876931"

  - `method.url` (string)
    The URL where the merchant should redirect the user to complete Credit Card Payments. This field is only applicable and available for credit card payment transactions.
    Example: "https://cc.easypay.pt/v3/public/card-details/cec55ab6-bda3-4ab3-af22-04d2ad2c046a"

  - `customer` (object)

## 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 404 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.