> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dintero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Optimizely (EPiServer)

> Install the Dintero Checkout module for Optimizely Commerce (EPiServer Commerce).

Install the Dintero Checkout module for Optimizely Commerce, formerly known as EPiServer Commerce.

## Prerequisites

* Optimizely Commerce (EPiServer Commerce) version 10.9 or later.
* A Dintero account with API keys and a payment profile. See [API client setup](https://docs.dintero.com/docs/checkout/checkout-client.md).

## Install the module

Add the `Dintero.Checkout.Episerver` library from the Optimizely NuGet repository.

The source code and reference implementation are available at [github.com/Dintero/Dintero.Checkout.Episerver](https://github.com/Dintero/Dintero.Checkout.Episerver).

## Configure the integration

**1. Create a configuration page layout**

Build a page layout named `ConfigurePayment.ascx` to manage these credentials from [Dintero Backoffice](https://backoffice.dintero.com):

* Account ID
* Client ID
* Client Secret
* Profile ID

**2. Check for conflicting meta fields**

Verify that a meta field named `DinteroSessionId` does not already exist in your system.

**3. Create a DinteroPage instance**

In EPiServer CMS, create a new instance of the `DinteroPage` page type.

**4. Configure redirect pages**

Add the following properties to your start page:

* `DinteroPaymentCancelPage`: the page users land on after a failed authorization.
* `DinteroPaymentLandingPage`: the page users land on after a successful authorization.

**5. Create the payment method**

Create a new payment method named `Dintero` with `Dintero` as the payment system identifier.

## Custom post-processing (optional)

Implement the `IPostProcessDinteroPayment` interface to add custom logic that runs after authorization, capture, or refund.

## Supported features

* Capture and partial refunds at item level within the EPiServer admin.

> [!NOTE]
>
> Changes made in Dintero Backoffice are not automatically synced to EPiServer order management. Always capture and refund through EPiServer to keep order state consistent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.