use serde::{Serialize, Deserialize};
use super::PaymentFlowsAmountDetails;
/**A PaymentIntent guides you through the process of collecting a payment from your customer.
We recommend that you create exactly one PaymentIntent for each order or
customer session in your system. You can reference the PaymentIntent later to
see the history of payment attempts for a particular session.
A PaymentIntent transitions through
[multiple statuses](https://stripe.com/docs/payments/intents#intent-statuses)
throughout its lifetime as it interfaces with Stripe.js to perform
authentication flows and ultimately creates at most one successful charge.
Related guide: [Payment Intents API](https://stripe.com/docs/payments/payment-intents)*/
#[derive(Debug, Clone, Serialize, Deserialize, Default)]
pub struct PaymentIntent {
///Amount intended to be collected by this PaymentIntent. A positive integer representing how much to charge in the [smallest currency unit](https://stripe.com/docs/currencies#zero-decimal) (e.g., 100 cents to charge $1.00 or 100 to charge ¥100, a zero-decimal currency). The minimum amount is $0.50 US or [equivalent in charge currency](https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts). The amount value supports up to eight digits (e.g., a value of 99999999 for a USD charge of $999,999.99).
pub amount: i64,
///Amount that can be captured from this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub amount_capturable: Option<i64>,
///
#[serde(skip_serializing_if = "Option::is_none")]
pub amount_details: Option<PaymentFlowsAmountDetails>,
///Amount that this PaymentIntent collects.
#[serde(skip_serializing_if = "Option::is_none")]
pub amount_received: Option<i64>,
///ID of the Connect application that created the PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub application: Option<serde_json::Value>,
///The amount of the application fee (if any) that will be requested to be applied to the payment and transferred to the application owner's Stripe account. The amount of the application fee collected will be capped at the total payment amount. For more information, see the PaymentIntents [use case for connected accounts](https://stripe.com/docs/payments/connected-accounts).
#[serde(skip_serializing_if = "Option::is_none")]
pub application_fee_amount: Option<i64>,
///Settings to configure compatible payment methods from the [Stripe Dashboard](https://dashboard.stripe.com/settings/payment_methods)
#[serde(skip_serializing_if = "Option::is_none")]
pub automatic_payment_methods: Option<serde_json::Value>,
///Populated when `status` is `canceled`, this is the time at which the PaymentIntent was canceled. Measured in seconds since the Unix epoch.
#[serde(skip_serializing_if = "Option::is_none")]
pub canceled_at: Option<i64>,
///Reason for cancellation of this PaymentIntent, either user-provided (`duplicate`, `fraudulent`, `requested_by_customer`, or `abandoned`) or generated by Stripe internally (`failed_invoice`, `void_invoice`, or `automatic`).
#[serde(skip_serializing_if = "Option::is_none")]
pub cancellation_reason: Option<String>,
///Controls when the funds will be captured from the customer's account.
pub capture_method: String,
/**The client secret of this PaymentIntent. Used for client-side retrieval using a publishable key.
The client secret can be used to complete a payment from your frontend. It should not be stored, logged, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.
Refer to our docs to [accept a payment](https://stripe.com/docs/payments/accept-a-payment?ui=elements) and learn about how `client_secret` should be handled.*/
#[serde(skip_serializing_if = "Option::is_none")]
pub client_secret: Option<String>,
///Describes whether we can confirm this PaymentIntent automatically, or if it requires customer action to confirm the payment.
pub confirmation_method: String,
///Time at which the object was created. Measured in seconds since the Unix epoch.
pub created: i64,
///Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Must be a [supported currency](https://stripe.com/docs/currencies).
pub currency: String,
/**ID of the Customer this PaymentIntent belongs to, if one exists.
Payment methods attached to other Customers cannot be used with this PaymentIntent.
If present in combination with [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage), this PaymentIntent's payment method will be attached to the Customer after the PaymentIntent has been confirmed and any required actions from the user are complete.*/
#[serde(skip_serializing_if = "Option::is_none")]
pub customer: Option<serde_json::Value>,
///An arbitrary string attached to the object. Often useful for displaying to users.
#[serde(skip_serializing_if = "Option::is_none")]
pub description: Option<String>,
///Unique identifier for the object.
pub id: String,
///ID of the invoice that created this PaymentIntent, if it exists.
#[serde(skip_serializing_if = "Option::is_none")]
pub invoice: Option<serde_json::Value>,
///The payment error encountered in the previous PaymentIntent confirmation. It will be cleared if the PaymentIntent is later updated for any reason.
#[serde(skip_serializing_if = "Option::is_none")]
pub last_payment_error: Option<serde_json::Value>,
///The latest charge created by this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub latest_charge: Option<serde_json::Value>,
///Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.
pub livemode: bool,
///Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Learn more about [storing information in metadata](https://stripe.com/docs/payments/payment-intents/creating-payment-intents#storing-information-in-metadata).
#[serde(skip_serializing_if = "Option::is_none")]
pub metadata: Option<serde_json::Value>,
///If present, this property tells you what actions you need to take in order for your customer to fulfill a payment using the provided source.
#[serde(skip_serializing_if = "Option::is_none")]
pub next_action: Option<serde_json::Value>,
///String representing the object's type. Objects of the same type share the same value.
pub object: String,
///The account (if any) for which the funds of the PaymentIntent are intended. See the PaymentIntents [use case for connected accounts](https://stripe.com/docs/payments/connected-accounts) for details.
#[serde(skip_serializing_if = "Option::is_none")]
pub on_behalf_of: Option<serde_json::Value>,
///ID of the payment method used in this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub payment_method: Option<serde_json::Value>,
///Information about the payment method configuration used for this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub payment_method_configuration_details: Option<serde_json::Value>,
///Payment-method-specific configuration for this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub payment_method_options: Option<serde_json::Value>,
///The list of payment method types (e.g. card) that this PaymentIntent is allowed to use.
pub payment_method_types: Vec<String>,
///If present, this property tells you about the processing state of the payment.
#[serde(skip_serializing_if = "Option::is_none")]
pub processing: Option<serde_json::Value>,
///Email address that the receipt for the resulting payment will be sent to. If `receipt_email` is specified for a payment in live mode, a receipt will be sent regardless of your [email settings](https://dashboard.stripe.com/account/emails).
#[serde(skip_serializing_if = "Option::is_none")]
pub receipt_email: Option<String>,
///ID of the review associated with this PaymentIntent, if any.
#[serde(skip_serializing_if = "Option::is_none")]
pub review: Option<serde_json::Value>,
/**Indicates that you intend to make future payments with this PaymentIntent's payment method.
Providing this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.
When processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).*/
#[serde(skip_serializing_if = "Option::is_none")]
pub setup_future_usage: Option<String>,
///Shipping information for this PaymentIntent.
#[serde(skip_serializing_if = "Option::is_none")]
pub shipping: Option<serde_json::Value>,
///For card charges, use [statement_descriptor_suffix](https://stripe.com/docs/payments/account/statement-descriptors#dynamic). Otherwise, you can use this value as the complete description of a charge on your customers' statements. It must contain at least one letter and be 1–22 characters long.
#[serde(skip_serializing_if = "Option::is_none")]
pub statement_descriptor: Option<String>,
///Provides information about a card payment that customers see on their statements. Concatenated with the prefix (shortened descriptor) or statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 22 characters for the concatenated descriptor.
#[serde(skip_serializing_if = "Option::is_none")]
pub statement_descriptor_suffix: Option<String>,
///Status of this PaymentIntent, one of `requires_payment_method`, `requires_confirmation`, `requires_action`, `processing`, `requires_capture`, `canceled`, or `succeeded`. Read more about each PaymentIntent [status](https://stripe.com/docs/payments/intents#intent-statuses).
pub status: String,
///The data that automatically creates a Transfer after the payment finalizes. Learn more about the [use case for connected accounts](https://stripe.com/docs/payments/connected-accounts).
#[serde(skip_serializing_if = "Option::is_none")]
pub transfer_data: Option<serde_json::Value>,
///A string that identifies the resulting payment as part of a group. Learn more about the [use case for connected accounts](https://stripe.com/docs/connect/separate-charges-and-transfers).
#[serde(skip_serializing_if = "Option::is_none")]
pub transfer_group: Option<String>,
}
impl std::fmt::Display for PaymentIntent {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> Result<(), std::fmt::Error> {
write!(f, "{}", serde_json::to_string(self).unwrap())
}
}