# Payment intents

> For the complete machine-readable documentation index, see [llms.txt](https://apidocs.chargebee.com/llms.txt).


A `payment_intent` is created to help you navigate the 3DS flow of collecting payment from your customer. It is necessary only for implementing 3DS flow using Chargebee.js.

#### Auto-expiry[](#auto-expiry)

All `payment_intent`s with `status` as `inited`, `in_progress` or `authorized` become `expired` after an **hour** automatically.

## Sample Payment intent

```json
{
  "amount": 5000,
  "created_at": 1517501515,
  "currency_code": "USD",
  "expires_at": 1517503315,
  "gateway": "chargebee",
  "gateway_account_id": "gw___test__KyVnGlSBWTQeudG",
  "id": "__test__KyVnHhSBWTQz2Cu__test__0DZayCQMcAwDkEIPpUrGwkiyL25s7W1X",
  "modified_at": 1517501515,
  "object": "payment_intent",
  "payment_method_type": "card",
  "status": "inited"
}
```

## Payment intents attributes

## Input Parameters

- `id` (required, string, max chars=150)
  Identifier for PaymentIntent.

- `status` (required, enumerated string)
  Current status of PaymentIntent.
  Possible enum values:
    - `inited`
      Intent is initialized.
    - `in_progress`
      Status will be in\_progress if the Active Payment Attempt state is in requires\_identification, requires\_challenge or requires\_redirection.
    - `authorized`
      3DS verification successfully completed.
    - `consumed`
      If any Chargebee operation such as create subscription etc. is completed using the intent, it will be in consumed state. Intent cannot be used if it's already in consumed state.
    - `expired`
      Intent has expired, since it was not consumed before the predefined time-out.

- `currency_code` (optional, string, max chars=3)
  The currency code (ISO 4217 format) of the amount used in transaction.

- `amount` (required, in cents, min=0)
  Amount(in cents) to be authorized for 3DS flow.

- `gateway_account_id` (optional, string, max chars=50)
  The gateway account used for performing the 3DS flow.

- `expires_at` (required, timestamp(UTC) in seconds)
  Timestamp indicating when the PaymentIntent will expire if left unconsumed.

- `reference_id` (optional, string, max chars=200)
  Reference for payment method at gateway. Only applicable when the PaymentIntent is created for cards stored in the gateway.

- `payment_method_type` (optional, enumerated string, default=card)
  The payment method of this intent
  Possible enum values:
    - `card`
      card
    - `ideal`
      ideal
    - `sofort`
      sofort
    - `bancontact`
      bancontact
    - `google_pay`
      google\_pay
    - `dotpay`
      dotpay
    - `giropay`
      giropay
    - `apple_pay`
      apple\_pay
    - `upi`
      upi
    - `netbanking_emandates`
      netbanking\_emandates
    - `paypal_express_checkout`
      paypal\_express\_checkout
    - `direct_debit`
      direct\_debit
    - `boleto`
      boleto
    - `venmo`
      Venmo
    - `amazon_payments`
      amazon\_payments
    - `pay_to`
      PayTo
    - `faster_payments`
      Faster Payments
    - `sepa_instant_transfer`
      SEPA Instant Transfer
    - `klarna_pay_now`
      Klarna Pay Now
    - `online_banking_poland`
      Online Banking Poland
    - `payconiq_by_bancontact`
      Payments made via Payconiq by Bancontact.
    - `electronic_payment_standard`
      Electronic Payment Standard
    - `kbc_payment_button`
      KBC Payment Button
    - `pay_by_bank`
      Pay By Bank
    - `trustly`
      Trustly
    - `stablecoin`
      Payments made via Stablecoin.
    - `kakao_pay`
      Payments made via Kakao Pay.
    - `naver_pay`
      Payments made via Naver Pay.
    - `revolut_pay`
      Payments made via Revolut Pay.
    - `cash_app_pay`
      Payments made via Cash App Pay.
    - `wechat_pay`
      Payments made via WeChat Pay.
    - `alipay`
      Payments made via Alipay.
    - `twint`
      Payments made via Twint
    - `go_pay`
      Payments made via GoPay
    - `grab_pay`
      Payments made via GrabPay
    - `pay_co`
      Payments made via PayCo
    - `after_pay`
      Payments made via Afterpay
    - `swish`
      Payments made via Swish
    - `payme`
      Payments made via PayMe
    - `pix`
      Pix
    - `klarna`
      Payments made via Klarna.
    - `alipay_hk`
      Payments made via Alipay HK.
    - `paypay`
      PayPay
    - `gcash`
      Payments made via GCash.
    - `south_korean_cards`
      Payments made via South Korean Cards
    - `paynow`
    - `bizum`
    - `promptpay`
    - `dana`
      Payments made via Dana.
    - `touch_n_go`
      Payments made via Touch 'n Go.
    - `tamara`
      Payments made via Tamara.
    - `qpay`
      Payments made via Qpay.
    - `ovo`
    - `momo`
    - `mercado_pago`
    - `nequi`
    - `nupay`
    - `picpay`
    - `thai_qr`
    - `blik`
    - `fpx`
    - `wero`
    - `p24`
    - `affirm_pay`
    - `rakuten_pay`

- `success_url` (optional, string, max chars=250)
  The URL the customer will be directed to once 3DS verification is successful. Applicable only when `payment_method_type` is `ideal` , `sofort` , `dotpay` or `giropay` .

- `failure_url` (optional, string, max chars=250)
  The URL the customer will be directed to when 3DS verification fails. Applicable only when `payment_method_type` is `ideal` , `sofort` , `dotpay` or `giropay` .

- `created_at` (required, timestamp(UTC) in seconds)
  Timestamp indicating when the PaymentIntent was created.

- `modified_at` (required, timestamp(UTC) in seconds)
  Timestamp indicating when the PaymentIntent was last modified.

- `resource_version` (optional, long)
  Version number of this resource. The `resource_version` is updated with a new timestamp in milliseconds for every change made to the resource. This attribute will be present only if the resource has been updated after 2016-09-28.

- `updated_at` (optional, timestamp(UTC) in seconds)
  Timestamp indicating when this payment intent was last updated.

- `payment_method_options` (optional, jsonobject)
  Options used to process the payment method. This attribute is omitted when no preference is stored.
  
  -   `card`: Options for card payments.
      -   `three_d_secure`: Options for 3DS authentication.
          -   `challenge_preference`: The preferred 3DS flow. Applicable only when `payment_method_type` is `card` and 3DS is enabled for the gateway account. Supported for Stripe, Adyen, and BlueSnap; ignored for other gateways. The gateway or card issuer can override the preference.
              -   `no_preference`: Chargebee, the gateway, and the issuer decide the 3DS flow.
              -   `no_challenge`: A frictionless flow without a challenge is requested.
              -   `challenge`: A challenge flow is requested.

- `customer_id` (optional, string, max chars=50)
  The unique identifier of the customer for whom the `payment_intent` will be created. If specified, the `payment_intent` will be used exclusively for that customer. If not specified, the `payment_intent` won't be associated with any customer and will be available for any customer.
  
  **See also**
  
  [Customer resource lookup and creation](/docs/api/payment_intents)

- `gateway` (optional, string)
  Gateway associated with the PaymentIntent.

- `business_entity_id` (optional, string, max chars=50)
  The ID of the business entity created for the site. For Product Catalog 1.0, all the site data is tied to this business entity.
  
  **Note**
  
  [Multiple Business Entities](/docs/api/getting-started) is a feature available only on Product Catalog 2.0.

- `brand_id` (optional, string, max chars=50)
  The unique ID of the [brand](/docs/api/brands) this payment intent belongs to. Unless a brand was specified in the request, this is the brand of the customer the payment intent was created for.

- `active_payment_attempt` (optional, payment_attempt)
  Active payment attempt for the PaymentIntent.
  - `id` (optional, string, max chars=70)
    Identifier for PaymentIntent's active payment attempt.
  - `status` (required, enumerated string)
    Current status of active payment attempt
    Possible enum values:
      - `inited`
        Payment attempt is initialized.
      - `requires_identification`
        Customer's device fingerprint is used to verify their identity. It needs to be sent to the Issuing Bank for verification.
      - `requires_challenge`
        The transaction has to go through 3DS Challenge flow and the customer needs to authenticate via 3DS 2.0
      - `requires_redirection`
        The transaction has to go through 3DS Redirection flow and the customer needs to authenticate via 3DS 1.0
      - `authorized`
        3DS verification successfully completed.
      - `refused`
        3DS verification attempt failed.
      - `pending_authorization`
        Waiting for the authorization.
  - `payment_method_type` (optional, enumerated string, default=card)
    The payment method of this attempt
    Possible enum values:
      - `card`
        card
      - `ideal`
        ideal
      - `sofort`
        sofort
      - `bancontact`
        bancontact
      - `google_pay`
        google\_pay
      - `dotpay`
        dotpay
      - `giropay`
        giropay
      - `apple_pay`
        apple\_pay
      - `upi`
        upi
      - `netbanking_emandates`
        netbanking\_emandates
      - `paypal_express_checkout`
        paypal\_express\_checkout
      - `direct_debit`
        direct\_debit
      - `boleto`
        boleto
      - `venmo`
        Venmo
      - `amazon_payments`
        amazon\_payments
      - `pay_to`
        PayTo
      - `faster_payments`
        Faster Payments
      - `sepa_instant_transfer`
        SEPA Instant Transfer
      - `klarna_pay_now`
        Klarna Pay Now
      - `online_banking_poland`
        Online Banking Poland
      - `payconiq_by_bancontact`
        Payconiq by Bancontact
      - `electronic_payment_standard`
        Electronic Payment Standard
      - `kbc_payment_button`
        KBC Payment Button
      - `pay_by_bank`
        Pay By Bank
      - `trustly`
        Trustly
      - `stablecoin`
        Stablecoin
      - `kakao_pay`
        Kakao Pay
      - `naver_pay`
        Naver Pay
      - `revolut_pay`
        Revolut Pay
      - `cash_app_pay`
        Cash App Pay
      - `wechat_pay`
        WeChat Pay
      - `alipay`
        Alipay
      - `twint`
        Twint
      - `go_pay`
        Go Pay
      - `grab_pay`
        Grab Pay
      - `pay_co`
        Pay Co
      - `after_pay`
        After Pay
      - `swish`
        Swish
      - `payme`
        PayMe
      - `pix`
        Payments made via Pix
      - `klarna`
        Payments made via Klarna.
      - `alipay_hk`
        Payments made via Alipay HK.
      - `paypay`
        PayPay
      - `gcash`
        Payments made via GCash.
      - `south_korean_cards`
        Payments made via South Korean Cards
      - `paynow`
      - `bizum`
      - `promptpay`
      - `dana`
        Payments made via Dana.
      - `touch_n_go`
        Payments made via Touch 'n Go.
      - `tamara`
        Payments made via Tamara.
      - `qpay`
        Payments made via Qpay.
      - `ovo`
      - `momo`
      - `mercado_pago`
      - `nequi`
      - `nupay`
      - `picpay`
      - `thai_qr`
      - `blik`
      - `fpx`
      - `wero`
      - `p24`
      - `affirm_pay`
      - `rakuten_pay`
  - `id_at_gateway` (optional, string, max chars=50)
    Reference of PaymentIntent at gateway
  - `error_code` (optional, string, max chars=100)
    Error code received from the payment gateway when the `payment_attempt` fails.
  - `error_text` (optional, string, max chars=65k)
    Error message received from the payment gateway on failure.
  - `checkout_details` (optional, string, max chars=65k)
    JSON-encoded object that includes customer and browser details collected during checkout.
  - `created_at` (required, timestamp(UTC) in seconds)
    Timestamp indicating when the active payment attempt was created.
  - `modified_at` (required, timestamp(UTC) in seconds)
    Timestamp indicating when the active payment attempt was last modified.
  - `routing_rule_id` (optional, string, max chars=50)
    The ID of the [Advanced Routing Rule](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/advanced-routing-rules) used to select the payment gateway for this payment attempt. The value is `0` when the default routing configuration is used. This attribute is not returned when no routing evaluation is available.
    
    **Note:**
    
    -   Applicable only when Advanced Routing Rules is enabled.
    -   Advanced Routing Rules is currently in **Private Beta**. Please reach out to [Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_api&utm_medium=content&utm_campaign=support) to enable this feature.
  - `payment_method_display_rule_id` (optional, string, max chars=50)
    The ID of the [Payment Method Display Rule](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/payment-method-display-rules) used to determine which payment methods are shown at checkout for this payment attempt. The value is `0` when the default payment method display configuration is used. This attribute is not returned when no payment method display evaluation is available.
    
    **Note:**
    
    -   Applicable only when Payment Method Display Rules is enabled.
    -   Payment Method Display Rules is currently in **Private Beta**. Please reach out to [Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_api&utm_medium=content&utm_campaign=support) to enable this feature.
  - `error_detail` (optional, gateway_error_detail)
    Comprehensive information regarding the error experienced during an unsuccessful or declined transaction. Learn more about [gateway error references](/docs/api/v2/pcv-1/gateway_error_references)
    - `request_id` (optional, string, max chars=100)
      This is a unique identifier assigned by the payment gateway. It is used to track the request at the payment gateway
    - `error_category` (optional, string, max chars=100)
      This parameter categorizes the type of error that occurred for the request. It helps in understanding whether the error is due to API error, validation, processing, network issues, and more
    - `error_code` (optional, string, max chars=100)
      A gateway-specific code that corresponds to the particular error encountered for the request. This code can be used for identifying the error in a standardized manner across the gateway's services
    - `error_message` (optional, string, max chars=65k)
      A message provided by the gateway that describes the nature of the error encountered
    - `decline_code` (optional, string, max chars=100)
      When a transaction is declined, this code is provided by the gateway to specify the reason for the decline
    - `decline_message` (optional, string, max chars=65k)
      This message gives a descriptive explanation of the reason for the transaction's decline
    - `network_error_code` (optional, string, max chars=100)
      This code represents errors that originate from the payment network (such as Visa, MasterCard, and more). It is different from the gateway error code and is specific to the network's error-handling system
    - `network_error_message` (optional, string, max chars=65k)
      This the network related error message from the gateway, this is a detailed message provided by the payment network explaining the nature of the network error encountered
    - `error_field` (optional, string, max chars=100)
      This parameter indicates which specific data field or attribute in the request caused the error
    - `recommendation_code` (optional, string, max chars=100)
      After an error has occurred, the gateway or payment network may provide a recommendation code. This code suggests a course of action or remedy that you can follow to resolve the issue
    - `recommendation_message` (optional, string, max chars=65k)
      This message is intended to provide guidance or suggestions on action or remedy that you can follow to resolve the issue
    - `processor_error_code` (optional, string, max chars=100)
      This code is provided by the payment processor (the entity that handles the transaction between the bank accounts and the payment networks) and indicates errors that occur at this stage of the payment process
    - `processor_error_message` (optional, string, max chars=65k)
      This message describes the specific error that the payment processor encountered
    - `error_cause_id` (optional, string, max chars=150)
      A [Chargebee-defined code](/docs/api/errors) that corresponds to the specific error encountered during the request. This code helps in identifying and standardizing the error across different gateway services for consistent error handling.
    - `processor_advice_code` (optional, string, max chars=100)
      Advice code returned by the payment gateway or processor that provides guidance on how to handle a declined transaction, for example, whether to retry or take a different action.

- `payment_attempts` (optional, list of payment_attempt)
  List of payment attempts associated with this PaymentIntent. Each item in the list is a `payment_attempt` object that shares the same structure as `active_payment_attempt`, except for the `routing_rule_id` and `payment_method_display_rule_id` attributes, which are returned only on `active_payment_attempt`.
  - `id` (optional, string, max chars=70)
    Identifier for the payment attempt.
  - `status` (required, enumerated string)
    Current status of the payment attempt.
    Possible enum values:
      - `inited`
        Payment attempt is initialized.
      - `requires_identification`
        Customer's device fingerprint is used to verify their identity. It needs to be sent to the Issuing Bank for verification.
      - `requires_challenge`
        The transaction requires the 3DS Challenge flow, where the customer completes authentication through an inline 3DS 2.0 challenge presented by their card issuer.
      - `requires_redirection`
        The transaction must go through the 3DS Redirection flow, where the customer is redirected to their card issuer's authentication page (3DS 1.0) to verify the payment. After authentication, the customer is redirected to the specified `[success_url](/docs/api/payment_intents/payment_intent-object#success_url)` or `[failure_url](/docs/api/payment_intents/payment_intent-object#failure_url)` .
      - `authorized`
        3DS verification successfully completed.
      - `refused`
        3DS verification attempt failed.
      - `pending_authorization`
        Waiting for the authorization.
  - `payment_method_type` (optional, enumerated string, default=card)
    The payment method of this attempt.
    Possible enum values:
      - `card`
        card
      - `ideal`
        ideal
      - `sofort`
        sofort
      - `bancontact`
        bancontact
      - `google_pay`
        google\_pay
      - `dotpay`
        dotpay
      - `giropay`
        giropay
      - `apple_pay`
        apple\_pay
      - `upi`
        upi
      - `netbanking_emandates`
        netbanking\_emandates
      - `paypal_express_checkout`
        paypal\_express\_checkout
      - `direct_debit`
        direct\_debit
      - `boleto`
        boleto
      - `venmo`
        Venmo
      - `amazon_payments`
        amazon\_payments
      - `pay_to`
        PayTo
      - `faster_payments`
        Faster Payments
      - `sepa_instant_transfer`
        SEPA Instant Transfer
      - `klarna_pay_now`
        Klarna Pay Now
      - `online_banking_poland`
        Online Banking Poland
      - `payconiq_by_bancontact`
        Payments made via Payconiq by Bancontact.
      - `electronic_payment_standard`
        Electronic Payment Standard
      - `kbc_payment_button`
        KBC Payment Button
      - `pay_by_bank`
        Pay By Bank
      - `trustly`
        Trustly
      - `stablecoin`
        Payments made via Stablecoin.
      - `kakao_pay`
        Payments made via Kakao Pay.
      - `naver_pay`
        Payments made via Naver Pay.
      - `revolut_pay`
        Payments made via Revolut Pay.
      - `cash_app_pay`
        Payments made via Cash App Pay.
      - `wechat_pay`
        Payments made via WeChat Pay.
      - `alipay`
        Payments made via Alipay.
      - `twint`
        Payments made via Twint
      - `go_pay`
        Payments made via GoPay
      - `grab_pay`
        Payments made via GrabPay
      - `pay_co`
        Payments made via PayCo
      - `after_pay`
        Payments made via Afterpay
      - `swish`
        Payments made via Swish
      - `payme`
        Payments made via PayMe
      - `pix`
        Pix
      - `klarna`
        Payments made via Klarna.
      - `alipay_hk`
        Payments made via Alipay HK.
      - `paypay`
        PayPay
      - `gcash`
        Payments made via GCash.
      - `south_korean_cards`
        Payments made via South Korean Cards
      - `paynow`
      - `bizum`
      - `promptpay`
      - `dana`
        Payments made via Dana.
      - `touch_n_go`
        Payments made via Touch 'n Go.
      - `tamara`
        Payments made via Tamara.
      - `qpay`
        Payments made via Qpay.
      - `ovo`
      - `momo`
      - `mercado_pago`
      - `nequi`
      - `nupay`
      - `picpay`
      - `thai_qr`
      - `blik`
      - `fpx`
      - `wero`
      - `p24`
      - `affirm_pay`
      - `rakuten_pay`
  - `id_at_gateway` (optional, string, max chars=50)
    Reference of the payment attempt at the gateway.
  - `error_code` (optional, string, max chars=100)
    Error code received from the payment gateway on failure.
  - `error_text` (optional, string, max chars=65k)
    Error message received from the payment gateway on failure.
  - `checkout_details` (optional, string, max chars=65k)
    JSON-encoded object that includes customer and browser details collected during checkout.
  - `created_at` (required, timestamp(UTC) in seconds)
    Timestamp indicating when the payment attempt was created.
  - `modified_at` (required, timestamp(UTC) in seconds)
    Timestamp indicating when the payment attempt was last modified.
  - `routing_rule_id` (optional, string, max chars=50)
    This attribute is not returned for historical payment attempts. See `active_payment_attempt.routing_rule_id`.
  - `payment_method_display_rule_id` (optional, string, max chars=50)
    This attribute is not returned for historical payment attempts. See `active_payment_attempt.payment_method_display_rule_id`.
  - `error_detail` (optional, gateway_error_detail)
    Comprehensive information regarding the error experienced during an unsuccessful or declined transaction. Learn more about [gateway error references](/docs/api/v2/pcv-1/gateway_error_references)
    - `request_id` (optional, string, max chars=100)
      This is a unique identifier assigned by the payment gateway. It is used to track the request at the payment gateway
    - `error_category` (optional, string, max chars=100)
      This parameter categorizes the type of error that occurred for the request. It helps in understanding whether the error is due to API error, validation, processing, network issues, and more
    - `error_code` (optional, string, max chars=100)
      A gateway-specific code that corresponds to the particular error encountered for the request. This code can be used for identifying the error in a standardized manner across the gateway's services
    - `error_message` (optional, string, max chars=65k)
      A message provided by the gateway that describes the nature of the error encountered
    - `decline_code` (optional, string, max chars=100)
      Code provided by the gateway that specifies the reason for the transaction decline.
    - `decline_message` (optional, string, max chars=65k)
      Descriptive message explaining the reason for the transaction's decline.
    - `network_error_code` (optional, string, max chars=100)
      This code represents errors that originate from the payment network (such as Visa, MasterCard, and more). It is different from the gateway error code and is specific to the network's error-handling system
    - `network_error_message` (optional, string, max chars=65k)
      This is the network-related error message from the gateway; a detailed message provided by the payment network explaining the nature of the network error encountered
    - `error_field` (optional, string, max chars=100)
      This parameter indicates which specific data field or attribute in the request caused the error
    - `recommendation_code` (optional, string, max chars=100)
      After an error has occurred, the gateway or payment network may provide a recommendation code. This code suggests a course of action or remedy that you can follow to resolve the issue
    - `recommendation_message` (optional, string, max chars=65k)
      This message is intended to provide guidance or suggestions on action or remedy that you can follow to resolve the issue
    - `processor_error_code` (optional, string, max chars=100)
      This code is provided by the payment processor (the entity that handles the transaction between the bank accounts and the payment networks) and indicates errors that occur at this stage of the payment process
    - `processor_error_message` (optional, string, max chars=65k)
      This message describes the specific error that the payment processor encountered
    - `error_cause_id` (optional, string, max chars=150)
      A [Chargebee-defined code](/docs/api/errors) that corresponds to the specific error encountered during the request. This code helps in identifying and standardizing the error across different gateway services for consistent error handling.
    - `processor_advice_code` (optional, string, max chars=100)
      Advice code returned by the payment gateway or processor that provides guidance on how to handle a declined transaction, for example, whether to retry or take a different action.

- `payment_intent_metadata` (optional, payment_intent_metadata)
  Details about the client and the request that Chargebee captured when the payment intent was confirmed.
  - `source` (required, enumerated string)
    The source of the request that confirmed the payment intent.
    Possible enum values:
      - `payment_method_helper`
        The request came from the Chargebee.js [Payment Method Helper](https://www.chargebee.com/docs/payments/2.0/card-components-and-helpers/payment-method-helper).
      - `card_components`
        The request came from Chargebee.js [Card Components](https://www.chargebee.com/docs/payments/2.0/card-components-and-helpers/card-components).
      - `checkout`
        The request came from [hosted checkout](https://www.chargebee.com/docs/billing/1.0/hosted-capabilities/hosted-checkout), including hosted checkout for [gift subscriptions](https://www.chargebee.com/docs/billing/1.0/subscriptions/gift-subscriptions#gift-subscription-workflow).
      - `collect_now`
        The request came from the [Collect Now](https://apidocs.chargebee.com/docs/api/v2/pcv-1/hosted_pages/collect-now) hosted page.
      - `portal`
        The request came from the [Self-Serve Portal](https://www.chargebee.com/docs/billing/1.0/hosted-capabilities/self-serve-portal).
      - `payment_components`
        The request came from Chargebee.js [Payment Components](https://www.chargebee.com/docs/payments/2.0/payment-components/overview).
  - `client_ip_address` (optional, string, max chars=50)
    The IP address from which the payment intent was confirmed.
  - `user_agent` (optional, string, max chars=1000)
    The [user agent string](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent) of the client from which the payment intent was confirmed.
  - `created_at` (optional, timestamp(UTC) in seconds)
    Timestamp indicating when Chargebee captured this metadata.