pub struct ClientSessionApiRequest {
pub customer_id: Option<String>,
pub order_id: Option<String>,
pub amount: Option<Value>,
pub customer: Option<CheckoutCustomerDetailsApiSchema>,
pub order: Option<OrderDetailsApiSchema>,
pub payment_method: Option<CheckoutPaymentMethodOptionsApiSchema>,
pub currency_code: Option<String>,
pub metadata: Option<Value>,
}Fields§
§customer_id: Option<String>A unique identifier for your customer.
Create a client session token with a customerId to enable the client-side SDK to retrieve and manage your customer’s saved payment methods. A client session token also enables saving payment methods against this customer id.
order_id: Option<String>Your reference for the payment.
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.
customer: Option<CheckoutCustomerDetailsApiSchema>More information associated with the customer.
order: Option<OrderDetailsApiSchema>More information associated with the order.
payment_method: Option<CheckoutPaymentMethodOptionsApiSchema>Enable certain options associated with the payment method.
currency_code: Option<String>The 3-letter currency code in ISO 4217 format.
e.g. use USD for US dollars.
metadata: Option<Value>Additional data to be used throughout the payment lifecycle.
A dictionary of key-value pairs where the values can only be strings or integers.
e.g. {"productId": 1001, "merchantId": "a13bsd62s"}