This article series covers the planning and implementation of the Stripe payment gateway implementation. The first article covered setting up the Admin interface and the class library used for the live site. The second article covered the Web API endpoint used to accept webhook messages form Stripe.

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.

This article series covers the planning and implementation of the Stripe payment gateway implementation.

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 previous article in this series covered the tools available for creating integrations, and the process of choosing which tools to use for the Stripe payment gateway integration. 

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. 

With the release of version 12 in 2018, Kentico made the switch from Web Forms-based Portal Engine to MVC as its primary development model. This opened the door for more flexible customization— having a separate front-end site allows developers to execute custom code from almost anywhere in that site’s lifecycle. However, sometimes more complex integrations need to tie in to the admin application as well, or don’t really make sense in the context of the live site, so it’s worth looking into the available tools for such scenarios.

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.

In this sample article, we will add a column to the users UniGrid list in the Users module. It is a practical example of creating extenders for module UI pages. This has been also discussed in our community forum, but this article will add a bit more complexity.

Currently, the product options price adjustments in Kentico Xperience E-commerce are applied to the resulting price only when used as standard options. This article will show you what customization needs to be done in order to take these adjustments into account also when generating the product variants in the administration interface.

When building your MVC site with Kentico, it’s possible you may run into page preview 404 or ” VirtualContextHashOrUserValidationFailed ” errors, with the latter message being somewhat misleading as to the cause of the error. Since there are more than a few things to check, this article will equip you with troubleshooting tools preparing you for battle with the page preview errors.

Kentico supports many kinds of authentication methods – from Forms authentication, Windows AD authentication to Claims-based authentication. In this article we will focus on Claims-based authentication and how to integrate Azure Active Directory as your identity provider.

If you’re running an E-Commerce store in Kentico, there’s a good chance you’ve used discount functionality. Seeing data about the various discounts you’ve applied can be difficult as this information is stored as XML markup in the database table for orders. In its raw form, data about discounts is stored on an order-by-order basis, and not in a very visually pleasant form. This article will go over the process of creating a report to display aggregated data about discounts.

By default, there are some restrictions on user names when registering in an MVC project. If you want to customize user name and password formats, a small code change is necessary.