Complete an order.
Documentation Index
Fetch the complete documentation index at: https://docs.nuwebgroup.com/llms.txt
Use this file to discover all available pages before exploring further.
The 'Bearer' token can be obtained from the token management interface or via the login endpoint using your admin user credentials.
The ID of the company this operation should be performed against.
Sets the preferred language for localised response content (e.g. en, fr, de). If the requested language is not supported by the company, the company fallback language will be assumed.
A list of attributes that you wish to be returned in the payload. When empty or omitted, all fields will be included by default. Use dot-notation for both top-level resources and child resources, i.e. orders.id,orderItems.saleItemId,venues.name. Can be used in conjunction with except providing both parameters don't reference the same resource.
A list of attributes that you wish to exclude from the payload. When empty or omitted, all fields will be included by default. Use dot-notation for both top-level resources and child resources, i.e. orders.id,orderItems.saleItemId,venues.name. Can be used in conjunction with only providing both parameters don't reference the same resource.
Request body for completing an order
The basket ID for which we want to complete an order. Basket IDs and Order IDs can be used interchangeably.
The payment method for the order. This will determine the transaction type for reporting purposes. This value will override the value stored against the supplied transactionId (if provided).
card-not-present-offline, card-not-present-online, card-present-offline, card-present-online, cash, complimentary, bank, ewallet-online, cheque, gift-card, money-order, split Breakdown of payments when using the 'split' payment method. The sum of all splits must equal the order total.
A payment plan object. This is currently only applicable for the processing of deposit payments. If a transanctionId is supplied, this must be omitted.
{ "type": "deposit" }If a customer can be found using this then customerName and customerEmail will be ignored.
Optional customer name, but required when the customer email doesn't already exist in the system.
Optional customer email. If this is present, fetch this user from the database and assign the order to this user.
This will be used in combination with customerName + customerEmail OR customerId. Single sign-on identifier for the customer, optional & only applicable to companies using a custom SSO solution.
Optional transaction ID. If supplied and valid, the matching transaction will be updated to success as part of completion. Use with capture=true when you want this endpoint to perform gateway capture for a deferred online payment.
Opt in to capture for deferred external gateway transactions as part of this endpoint. Defaults to false for backwards compatibility. This only applies when transactionId references an existing gateway-backed transaction (for example card-not-present online or split payments containing a gateway split). Non-gateway methods such as cash are unaffected. Account balance payments (e.g. ewallet-online) are processed regardless of this flag. If capture cannot be confirmed, the request returns a 422 validation error, the order remains incomplete, and the existing transaction remains open for retry.
Pass true if you want to prevent sending the order confirmation email, otherwise pass false or omit this property completely.
You should provide the payment media ID that is responsible for this transaction (for accurate epos and wallet balance reporting).
Successfully completed order.