A unique identifier for this specific event. This ensures that each event can
be tracked and processed individually.
Describes the type of event. In this case, it signifies that a payment intent
is successful.
The timestamp when the event was generated, typically in milliseconds since
the Unix epoch (January 1, 1970). This value can be used to track when the
event occurred.
A unique identifier for the specific payment intent. This ID ties the event
back to a particular transaction or payment process that triggered the event.
Represents the current status of the payment intent. For this event, the
status will be
SUCCESS
.The amount involved in the transaction, typically expressed in the smallest
unit of the currency. Here, 100 represents 1.00 USD (because USD typically
uses two decimal places).
The currency used for the transaction. In this case, it is United States
Dollars (USD).
The payment method used for the transaction. supported payment
methods
Contains information about the customer who made the payment:
- name: The full name of the customer
- email: The email address of the customer
- contactNumber: The contact phone number of the customer
Contains details about the card used for the transaction:
- brand: The brand of the card (e.g., Visa, Mastercard).
- country: The issuing country of the card.
- lastFourDigit: The last four digits of the card number.
- expiryMonth: The expiration month of the card.
- expiryYear: The expiration year of the card.
- fundingType: The type of card funding, such as Credit or Debit.
A collection of key-value pairs that were provided when the object was
created. These metadata values are echoed back in the response, allowing you
to store and retrieve custom information such as context-specific attributes,
references, or tags. This can be useful for correlating records in your system
or attaching meaningful context to transactions.