Integration Patterns Smart Checkout


The following questions should be answered:

  • Is the business case very simple or more complex?

  • Is the checkout process started from a shop or website?

  • Is it appropriate for you to check the basket items in detail?

If you are a market place, you arrange the sales for many contracted merchants. Thus you need to send a mixed basket. Only the API integration has this option so far.

The checkout can be integrated in your webshop, or a specialized web application. But it could also be started standalone in the customer's browser by handing him out a URL. It you be sent via e-mail or as QR code, for instance.

If the basket is conveyed using the API, you can trust it better than if it is passed via HTML or JavaScript.

Assessment Help

The following table can help the merchant and the sales team to assess with of the different patterns matches the merchant's needs best.





Development Skills





WS integration (REST API)




Merchant's website

needed to start


static return possible

dynamic return possible



Trust in basket3

needs check

can be trusted

1) The URL can be used with or without the merchant's storefront application (also printed as QR code, sent via chat, mail, etc.). You can also return the user to a webpage, even if he started via URL without any storefront application of the merchant.
2) The HTML/HTML and the JS/JS allow a dynamic return URL too. But to really benefit from it, the merchant's website need to implement some handling. This would need some programming skills.
3) When the basket is passed in the frontend, the merchant should check the details before the order is accepted. In the Checkout Wizard the basket cannot be changed anymore, and can be trusted.