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.
The currency code (ISO 4217 format) of the amount used in transaction.
The gateway account used for performing the 3DS flow.
Timestamp indicating when the PaymentIntent will expire if left unconsumed.
Reference for payment method at gateway. Only applicable when the PaymentIntent is created for cards stored in the gateway.
The payment method of this intent
card
ideal
sofort
bancontact
google_pay
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
.
The URL the customer will be directed to when 3DS verification fails. Applicable only when payment_method_type
is ideal
, sofort
, dotpay
or giropay
.
Timestamp indicating when the PaymentIntent was created.
Timestamp indicating when the PaymentIntent was last modified.
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.
Timestamp indicating when this payment intent was last updated.
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