pub struct CapturePaymentForOrderResponse {
pub create_time: Option<String>,
pub update_time: Option<String>,
pub id: Option<String>,
pub payment_source: Option<PaymentSourceResponse>,
pub intent: Option<OrderIntent>,
pub payer: Option<Payer>,
pub purchase_units: Option<Vec<PurchaseUnit>>,
pub status: Option<OrderStatus>,
pub links: Option<Vec<LinkDescription>>,
}Fields§
§create_time: Option<String>The date and time when the transaction occurred, in Internet date and time format.
update_time: Option<String>The date and time when the transaction occurred, in Internet date and time format.
id: Option<String>The ID of the order.
payment_source: Option<PaymentSourceResponse>The payment source used to fund the payment.
intent: Option<OrderIntent>The intent to either capture payment immediately or authorize a payment for an order after order creation.
payer: Option<Payer>The customer who approves and pays for the order. The customer is also known as the payer.
purchase_units: Option<Vec<PurchaseUnit>>An array of purchase units. Each purchase unit establishes a contract between a customer and merchant. Each purchase unit represents either a full or partial order that the customer intends to purchase from the merchant.
status: Option<OrderStatus>The order status.r.
links: Option<Vec<LinkDescription>>An array of request-related HATEOAS links. To complete payer approval, use the approve link to redirect the payer. The API caller has 3 hours (default setting, this which can be changed by your account manager to 24/48/72 hours to accommodate your use case) from the time the order is created, to redirect your payer. Once redirected, the API caller has 3 hours for the payer to approve the order and either authorize or capture the order. If you are not using the PayPal JavaScript SDK to initiate PayPal Checkout (in context) ensure that you include application_context.return_url is specified or you will get “We’re sorry, Things don’t appear to be working at the moment” after the payer approves the payment.