Sample Payment intentJSON
Payment intents attributes
Current status of PaymentIntent.
Intent is initialized.
Status will be in_progress if the Active Payment Attempt state is in requires_identification, requires_challenge or requires_redirection.
3DS verification successfully completed.
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.
Intent has expired, since it was not consumed before the predefined time-out.
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 whenpayment_method_typeiscardand 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.
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.
The unique ID of the business entity
of this payment_intent
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.