# Shows subscription payment details

Retrieves the subscription payment details
**Required scope:** <code style="background:#e8f0fe;color:#1a73e8;padding:2px 8px;border-radius:12px;font-size:0.85em">subscription:read</code>

Endpoint: GET /subscription/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Response 200 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` (string)
    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.id` (string)
    Example: 1b4ca1cf-9a1a-415b-97bf-342c6ddcf9c1

  - `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.key` (string)
    Example: subscription 01234589

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

  - `method` (object)

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

  - `method.status` (string)
    Enum: "active", "inactive", "waiting"

  - `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
    Example: PT50002700000001234567833

  - `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 401 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 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.

