The last article will focus on the process of getting funds from orders that use delayed capture, implementing a helper class and an event handler to serve this purpose.

The previous article covered the process of creating necessary settings categories and keys, adding resource strings to the Xperience admin app, and adding Stripe Checkout to the live site.

The admin library of this integration has two main tasks to accomplish. First, it needs to accept webhook requests from Stripe and update Xperience orders appropriately. Second, it needs to capture funds for payments using delayed capture.

This article will focus on the first part, which is one of the most vital to the integration. With the live site code alone, orders can be paid for through stripe, but there is no way to automatically propagate that information back to Kentico. Store staff would have to manually keep track of orders and update them according to data in Stripe. We’ll create an endpoint so that Stripe webhooks can automatically keep our Xperience orders up to date.

The rest of the series will cover the implementation of this integration, so you can code along and learn from the process. This first article will cover the setup in the admin interface and the class library used for the live site. 

If you want to use the integration without any coding, you can find it here. 

In this article, the first of a two-part series, I’ll summarize the various integration options for the admin application in Kentico Xperience 13, and use the Stripe payment gateway integration as an example for how the right tools can be selected. The next article in the series will cover the specifics of integrating payment gateways, using Stripe as an example.