Skip to content
This repository has been archived by the owner on Apr 23, 2021. It is now read-only.

Latest commit

 

History

History
20 lines (15 loc) · 3.89 KB

CreateCheckoutRequest.md

File metadata and controls

20 lines (15 loc) · 3.89 KB

SquareConnect.CreateCheckoutRequest

Description

Defines the parameters that can be included in the body of a request to the CreateCheckout endpoint.

Properties

Name Type Description Notes
idempotency_key String A unique string that identifies this checkout among others you've created. It can be any valid string but must be unique for every order sent to Square Checkout for a given location ID. The idempotency key is used to avoid processing the same order more than once. If you're unsure whether a particular checkout was created successfully, you can reattempt it with the same idempotency key and all the same other parameters without worrying about creating duplicates. We recommend using a random number/string generator native to the language you are working in to generate strings for your idempotency keys. See the Idempotency guide for more information.
order CreateOrderRequest The order including line items to be checked out.
ask_for_shipping_address Boolean If `true`, Square Checkout will collect shipping information on your behalf and store that information with the transaction information in your Square Dashboard. Default: `false`. [optional]
merchant_support_email String The email address to display on the Square Checkout confirmation page and confirmation email that the buyer can use to contact the merchant. If this value is not set, the confirmation page and email will display the primary email address associated with the merchant's Square account. Default: none; only exists if explicitly set. [optional]
pre_populate_buyer_email String If provided, the buyer's email is pre-populated on the checkout page as an editable text field. Default: none; only exists if explicitly set. [optional]
pre_populate_shipping_address Address If provided, the buyer's shipping info is pre-populated on the checkout page as editable text fields. Default: none; only exists if explicitly set. [optional]
redirect_url String The URL to redirect to after checkout is completed with `checkoutId`, Square's `orderId`, `transactionId`, and `referenceId` appended as URL parameters. For example, if the provided redirect_url is `http://www.example.com/order-complete&#x60;, a successful transaction redirects the customer to: <pre><code>http://www.example.com/order-complete?checkoutId&#x3D;xxxxxx&amp;amp;orderId&#x3D;xxxxxx&amp;amp;referenceId&#x3D;xxxxxx&amp;amp;transactionId&#x3D;xxxxxx&lt;/code&gt;&lt;/pre> If you do not provide a redirect URL, Square Checkout will display an order confirmation page on your behalf; however Square strongly recommends that you provide a redirect URL so you can verify the transaction results and finalize the order through your existing/normal confirmation workflow. Default: none; only exists if explicitly set. [optional]
additional_recipients [ChargeRequestAdditionalRecipient] The basic primitive of multi-party transaction. The value is optional. The transaction facilitated by you can be split from here. If you provide this value, the `amount_money` value in your additional_recipients must not be more than 90% of the `total_money` calculated by Square for your order. The `location_id` must be the valid location of the app owner merchant. This field requires `PAYMENTS_WRITE_ADDITIONAL_RECIPIENTS` OAuth permission. This field is currently not supported in sandbox. [optional]
note String An optional note to associate with the checkout object. This value cannot exceed 60 characters. [optional]