# Create subscription payment

Creates a Subscription.

Endpoint: POST /subscription
Version: 2.0
Security: accountId, apiKey

## Request fields (application/json):

  - `frequent_id` (string)
    Only required to create a subscription 
from an active Frequent Payment.
Some properties like 
customer and sdd_mandate 
are inherited by the subscriptions. 
So it's not necessary to send them in the request creation.
    Example: "9234ef0f-b666-41cc-8ad2-5b54c1a84150"

  - `capture` (object)

  - `capture.transaction_key` (string)
    The internal key used to identify this transaction in the merchant's database.

  - `capture.account` (object)
    For multi-account clients.

  - `capture.account.id` (string)
    The uuid of the account.

  - `capture.descriptive` (string)
    The description of the capture. Will be displayed in the bank statement or in the MB WAY application.

  - `expiration_time` (string)
    The last possible time to make the payment.
Required only when max_captures
and/or unlimited_payments
are NOT set.
    Example: "2037-12-12 16:05"

  - `currency` (string)
    The currency code in ISO 4217 format (e.g., "EUR" for Euro). This field specifies the type of currency used in financial operation.

  - `customer` (object)
    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)
    The merchant's key for identifying the payment.
    Example: "Example Key"

  - `value` (number, required)
    The payment value.Will be rounded to 2 decimals.
    Example: 12.55

  - `frequency` (string, required)
    Defining the frequency that the cycles are charged.
    Enum: "1D", "1W", "2W", "1M", "2M", "3M", "4M", "6M", "1Y", "2Y", "3Y"

  - `max_captures` (integer)
    Defining the total of cycles that will be charged.
Required only when expiration_time
and/or unlimited_payments
are NOT set.

  - `unlimited_payments` (boolean)
    When this property is set, unlimited cycles will be charged until the subscription is inactivated or deleted.

  - `start_time` (string, required)
    Defining the start of billing cycles.
    Example: "2027-01-11 16:05"

  - `failover` (boolean)
    After all retries failed, the payment cycle can have another try with another single method.

  - `capture_now` (boolean)
    Whether to schedule an immediate capture and schedule the second one for start_time.

  - `retries` (integer)
    Number of tries for every cycle of payments.
The maximum number of retries that can occur will be determined by the frequency that is selected.
If a capture is unsuccessful for any reason, it will attempt to charge once more until the allotted number of attempts is reached.

  - `method` (string, required)
    The payment methods.
    Enum: "cc", "dd"

  - `sdd_mandate` (object)
    The SDD Mandate object contains the necessary fields to create a SEPA Direct Debit mandate. This object ensures that all required information is provided to authorize and process SEPA Direct Debit transactions. Object required when method is Direct Debit.

  - `sdd_mandate.iban` (string, required)
    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, required)
    Full name of the account holder as it appears on the bank account.
    Example: "John Doe"

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

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

  - `sdd_mandate.account_holder` (string, required)
    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"

  - `sdd_mandate.country_code` (string)
    ISO 3166-1 alpha-2 country code of the customer's country.
    Example: "PT"

  - `sdd_mandate.max_num_debits` (string)
    Maximum number of debits allowed under this mandate.
    Example: "12"

  - `sdd_mandate.billing_entity` (string)
    The entity responsible for billing in the context of the SEPA Direct Debit (SDD) mandate.
    Example: "PT16103627"

## Response 201 fields (application/json):

  - `id` (string)
    Example: "458b2fc4-3092-4de3-abd4-fe1600c09420"

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

  - `key` (string)
    Example: "payment 02536985"

  - `expiration_time` (string)
    Example: "2099-01-15 00:00"

  - `start_time` (string)
    Example: "2027-01-15 00:00"

  - `frequency` (any)
    Enum: "1D", "1W", "2W", "1M", "2M", "3M", "4M", "6M", "1Y", "2Y", "3Y"

  - `retries` (integer)
    Example: 2

  - `max_captures` (integer)
    Example: 12

  - `failover` (boolean)

  - `capture_now` (boolean)

  - `unlimited_payments` (boolean)

  - `customer` (object)
    The Customer object contains detailed information about the customer involved in the transaction.

  - `customer.name` (string)
    Example: "Joey Price"

  - `customer.email` (string)
    Example: "john.doe@yahoo.com"

  - `customer.phone` (string)
    Example: "911234567"

  - `customer.phone_indicative` (string)
    Example: "+351"

  - `customer.fiscal_number` (string)
    Example: "PT921839198892623010"

  - `customer.language` (string)
    Example: "PT"

  - `method` (object)

  - `method.type` (any)
    Enum: "CC", "DD"

  - `method.url` (string)
    Example: "https://cc.easypay.pt/v3/public/card-details/cec55ab6-bda3-4ab3-af22-04d2ad2c046a"

  - `method.last_four` (string)
    Example: "2222"

  - `method.card_type` (string)
    Example: "VISA"

  - `method.expiration_date` (string)
    Example: "07/29"

  - `method.sdd_mandate` (object)
    SDD Mandate information as returned in detail responses

  - `method.sdd_mandate.id` (string)
    Mandate ID
    Example: "50389142122"

  - `method.sdd_mandate.iban` (string)
    International Bank Account Number (IBAN) in standard format

  - `method.sdd_mandate.key` (string)
    Mandate key
    Example: "Sdd mandate Key Example"

  - `method.sdd_mandate.name` (string)
    Account holder name
    Example: "John Doe"

  - `method.sdd_mandate.email` (string)
    Account holder email
    Example: "john.doe@easypay.pt"

  - `method.sdd_mandate.phone` (string)
    Account holder phone
    Example: "911345678"

  - `method.sdd_mandate.account_holder` (string)
    Account holder name as registered with bank
    Example: "John Doe"

  - `method.sdd_mandate.country_code` (string)
    Country code
    Example: "PT"

  - `method.sdd_mandate.max_num_debits` (string)
    Maximum number of debits allowed
    Example: "12"

  - `method.sdd_mandate.billing_entity` (string)
    Billing entity identifier
    Example: "PT16103627"

  - `method.sdd_mandate.reference_adc` (string)
    Example: "987654321123"

  - `transactions` (array)

  - `transactions.id` (string)
    Unique identifier for the transaction
    Example: "4fb3ac57-c7fe-4157-aeb7-4362ae24deec"

  - `transactions.key` (string)
    Merchant identification key
    Example: "Merchant identification key"

  - `transactions.created_at` (string)
    When the transaction was created
    Example: "2025-05-30T17:21:46Z"

  - `transactions.date` (string)
    Transaction date
    Example: "2025-05-30T17:21:47Z"

  - `transactions.values` (object)
    Transaction value breakdown

  - `transactions.values.requested` (number)
    Requested amount
    Example: 12.55

  - `transactions.values.paid` (number)
    Amount actually paid
    Example: 12.55

  - `transactions.values.fixed_fee` (number)
    Fixed fee charged
    Example: 0.07

  - `transactions.values.variable_fee` (number)
    Variable fee charged
    Example: 0.09

  - `transactions.values.tax` (number)
    Tax amount
    Example: 0.04

  - `transactions.values.transfer` (number)
    Amount transferred to merchant
    Example: 12.35

  - `transactions.transfer_date` (string)
    When the transfer occurred
    Example: "2025-06-02T00:00:00Z"

  - `transactions.transfer_batch` (string)
    Transfer batch identifier

  - `transactions.method` (string)
    Payment method used
    Example: "mbw"

  - `transactions.document_number` (string)
    Document number for the transaction
    Example: "MARCEL0208220628294020250530172147"

  - `transactions.descriptive` (string)
    Transaction description
    Example: "Descriptive Josefa"

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

  - `value` (number)
    Example: 10.55

  - `created_at` (string)
    Example: "2025-08-05 13:44:29"

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