If you don't support separate authorization and capture, then the value is always sale. If you support payment authorization, then this value is set based on the merchant's configuration. For more information on the customer field, refer to the customer hash.Įither sale or authorization. If customer is included, then at least one of customer.email or customer.phone_number is present. Refer to payment_method hash for more information.Ĭan be used to order payment attempts that are a part of the same group. Hash giving details on the payment method used. IETF BCP 47 language tag representing the language used by the merchant. Indicates whether the payment is in test or live mode. The value is always sent using a decimal point as a separator, regardless of locale. Your app must only call the PaymentSessionResolve once per id and group. As a result, Shopify can initiate multiple payment flows for the same id and group, redirecting to your app each time. All of those tabs will be associated with the same group. Identifies the payment when communicating with Shopify (in GraphQL mutations, for example).Ī customer might open multiple tabs in their browser for a given order.
This ID must be surfaced to the merchant so that they can correlate Shopify orders with payments managed by the Partner app.
It can be assumed that requests with a given ID are identical to any previously received requests with the same ID. Unique identifier for the payment attempt. Request body Anchor link to section titled "Request body" Attribute
0 kommentar(er)
