Commit CheckoutSession

It closes the order and confirms all Wapping transactions that have been applied. This registers the order information on the platform. In this step is important to check the integrity of the data, to inform the correct amounts, discounts applied (external to wapping and the ones from wapping), shipping amounts and the tax excluded amounts. The final amount registered should be the same as the one registered in the caller system (POS, ecommerce, etc). It follows this calculation: TotalAmount = Sum(OrderLines.Amount) + ShippingAmount - DiscountAmount

It's important to inform the external and internal (from Wapping) discounts applied correctly, to register the final amounts applied: If applies in the OrderLine level: OrderLine amount should have the discount applied, and it should be specified in the OrderLine.Discounts array. If applies in the Order level: It has to be added to the DiscountAmount, and specified in the CheckoutSessionCommitRequest.Discounts Important: order level discounts are different from Payment Methods, if the Wapping benefit applies as a Payment Method, it should be informed in the payments array, and not in the discounts section. If they are not supported as payment methods, then treat them as order discounts as explained.

        This process works asyncronously, the information is queued to be logged and processed in a backend process, but the response from this method will be syncronous, indicating the result of the operation.
        <p>
        The digitalization of the order can be done in the controller Order/CreateOrderReceipt
        </p>
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required

A unique identifier to reference the Checkout Session. This is returned when the CheckoutSession is created

Body Params

The order purchased by the customer

date-time

Date assigned to the order

string

Order identifier within business

payments
array of objects

Payment methods used in the order.

payments
string

Receipt language

Headers
string
enum
Defaults to application/json-patch+json

Generated from available request content types

Allowed:
Responses

500

Server Error

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json