Struct primer_api::model::PaymentApiResponse
source · [−]pub struct PaymentApiResponse {Show 15 fields
pub order: Option<OrderDetailsApiSchema>,
pub processor: Option<PaymentResponseProcessorApiSchema>,
pub date: Option<String>,
pub payment_method: Option<PaymentResponsePaymentMethodOptionsApiSchema>,
pub amount: Option<Value>,
pub status_reason: Option<StatusReasonApiSchema>,
pub transactions: Option<Vec<TransactionOverviewApiSchema>>,
pub id: Option<String>,
pub status: Option<String>,
pub required_action: Option<PaymentRequiredActionApiSchema>,
pub metadata: Option<Value>,
pub order_id: Option<String>,
pub currency_code: Option<String>,
pub customer_id: Option<String>,
pub customer: Option<CustomerDetailsApiSchema>,
}Fields
order: Option<OrderDetailsApiSchema>More information associated with the order.
processor: Option<PaymentResponseProcessorApiSchema>More information associated with the payment processor, including the processor name.
date: Option<String>The date and time at which the payment was created in UTC format.
payment_method: Option<PaymentResponsePaymentMethodOptionsApiSchema>The payment method options provided in the request, as well as the token used to process the payment.
amount: Option<Value>The amount you charged the customer, in minor units.
status_reason: Option<StatusReasonApiSchema>Check this field for more information regarding the payment’s status. This is especially useful when the status is DECLINED or FAILED.
transactions: Option<Vec<TransactionOverviewApiSchema>>A list summarizing the transactions that occurred while processing the payment.
Note: a refund is a separate transaction and so will appear in this transactions list if a refund was performed.
id: Option<String>The unique payment ID.
You can use this ID to retrieve the payment details, or perform downstream operations.
status: Option<String>See the payment status table for more information.
required_action: Option<PaymentRequiredActionApiSchema>Required action to perform in order to resume the payment workflow. This can be requiring a 3DS check from the customer for instance.
metadata: Option<Value>Additional data to be used throughout the payment lifecycle.
order_id: Option<String>Your reference for the payment.
currency_code: Option<String>The 3-letter currency code in ISO 4217 format.
e.g. use USD for US dollars.
customer_id: Option<String>The unique identifier for your customer.
customer: Option<CustomerDetailsApiSchema>More information associated with the customer.