pub struct ClientSessionWithTokenApiResponse {
pub amount: Option<Value>,
pub order_id: Option<String>,
pub client_token_expiration_date: Option<String>,
pub client_token: Option<String>,
pub order: Option<OrderDetailsApiSchema>,
pub customer_id: Option<String>,
pub customer: Option<CustomerDetailsApiSchema>,
pub payment_method: Option<CheckoutPaymentMethodOptionsApiSchema>,
pub currency_code: Option<String>,
pub warnings: Option<ClientSessionWarningsApiResponse>,
pub metadata: Option<Value>,
}
Fields§
§amount: Option<Value>
The amount you would like to charge the customer, in minor units. e.g. for $7, use 700
.
Some currencies, such as Japanese Yen, do not have minor units. In this case you should use the value as it is, without any formatting. For example for ¥100, use 100
.
If the amount is provided on this level, it would override any amount calculated from the provided line items, shipping and other amounts.
order_id: Option<String>
Your reference for the payment.
client_token_expiration_date: Option<String>
Expiration date & time of the client token (UTC with no timezoneinfo).
client_token: Option<String>
Client token used to initialize the SDK on all platforms.
order: Option<OrderDetailsApiSchema>
More information associated with the order.
customer_id: Option<String>
A unique identifier for your customer.
customer: Option<CustomerDetailsApiSchema>
More information associated with the customer.
payment_method: Option<CheckoutPaymentMethodOptionsApiSchema>
Enable certain options associated with the payment methods.
currency_code: Option<String>
e.g. use USD
for US dollars.
warnings: Option<ClientSessionWarningsApiResponse>
Warning messages to indicate missing information that are required for payment methods, checkout modules and other features; or when third-party services are unavailable.
metadata: Option<Value>
Additional data to be used throughout the payment lifecycle.