What is a Checkout?

A Checkout is the payment screen your customers see when they are about to pay. Each checkout can:

• Show different payment methods (card, Bizum, PayPal, crypto, etc.)
• Be shown only to certain customers based on segmentation rules (country, language, device type, currency...)
• Have its own appearance through reusable themes
• Connect to Connections or Orchestrations to process the payment

The conceptual chain is:

Checkout → contains Methods → each method is assigned to a Connection or an Orchestration that decides how to process the payment.

How to find and manage your Checkouts

In the panel: side menu → Optimization block → Checkouts.

The list

The list has two tabs, Active and Inactive, and two view modes:

• Grid view: each checkout is shown as a card with a real preview of the payment screen (mockup with amount, methods and form), its name, the icons of the active methods and a badge with its segmentation constraint.
• List view: a table with the columns Name, Payment methods, Show for and Last modified.

Creating a Checkout

Click the "Create Checkout" button in the top right. The editor opens directly with a new blank checkout ready to configure.

The Checkout editor

When you open a Checkout (or create a new one) the split-view editor opens. The screen is divided into three areas:

• Top header: an arrow to go back to the list, the last updated date, the checkout name with its dropdown and the Publish button.
• Left sidebar with four vertical tabs: Segmentation, Methods, Appearance, Settings.
• Right panel with a live preview of the checkout that updates with every change.

🧐 The checkout is not enabled or disabled from the header. That is done from the Settings tab, with Activate checkout.

Tab 1: Segmentation

Defines who this checkout will be shown to. Useful when you have several checkouts and want each one to appear under different conditions (for example, one for Spain and another for LATAM).

How it works

The section is titled Checkout segmentation, and inside it, under the "Show to:" label, you add the conditions that are evaluated when showing the checkout. You add them with Add condition.

• If it is the default checkout, you cannot segment it. The panel says so: "Default checkouts cannot be segmented and are used only when the segmentation requirements of the custom checkouts are not met".
• If you add a variable, the checkout is only shown when that variable is met.
• You can add several variables; all of them are evaluated with AND.

Available variables (18)

Operation (9): Price, Currency, Type (Single Payment / Subscription / Authorization), Language, Authorize only, MOTO, Partial approval, POS, POS Terminal.

Customer (9): Custom variable, Device type, OS, Browser, IP country, IP region, Country, Region, Email.

Tab 2: Methods

Defines which payment methods appear in the checkout and in what order. The panel sums it up as: "Select and arrange the payment methods you want to appear in your checkout".

Quick Payments

Fast methods based on browser or operating system wallets. They are only shown if there is a Card type method configured in the checkout:

• Apple Pay (on/off toggle)
• Google Pay (on/off toggle)

Payment methods

The list of available methods. Each row leads with the method, not with whoever processes it. For each one you will see:

• Drag handles to reorder them by dragging.
• The method logo and name in bold (Card, Bizum, Pepper, Finance...).
• Below, in small text, the source of the method: Provider - Account if it goes against a direct connection (for example Adyen - Adyen or Redsys - Bizum), or Orchestration - Name if it goes against an orchestration (for example Orchestration - Bizum).
• A toggle to enable or disable the method.
• The ||| icon that opens the per-method configuration.

You can add methods with the "Add card" and "Add method" buttons.

🧐 Besides card orchestrations, here you can use Financing and Alternative method orchestrations. In the list they are identified by their method, so a row tells you what the checkout offers, not who settles it.

Per-method configuration (||| icon)

Clicking the ||| icon opens the "Payment method configuration" modal, with two tabs and a Preview area at the top that reflects changes immediately.

At the bottom of the modal you have Delete, to remove the method from the checkout, plus Cancel and Save. Inside the Appearance tab there is also a Reset default values link.

Appearance tab

Customize how the method looks in the checkout. The options vary depending on the method:

• Card: Text in selector and Icon in selector (recommended size 70x70px). It has no button mode because it is always rendered with its embedded form.
• All other methods, including financing and alternative method ones: the same as Card, plus the Selector / Button toggle, Button background color and Logo in button.

Conditions tab

Defines who this method is shown to individually within the checkout. This creates a two-level segmentation model:

• At checkout level (Segmentation tab): you decide who to show the whole checkout to.
• At method level (this tab): you decide which methods appear inside the checkout for each customer.

Logic toggle:

• Show if → the method appears only if the condition is met.
• Not show if → the method is hidden if the condition is met.

The available variables are the same as in Segmentation: Operation (9) + Customer (9).

Typical use cases:

• Show Bizum only if IP country = ES.
• Show Pepper only if Price > 60 EUR.

Tab 3: Appearance

Management of reusable Themes across checkouts.

• "New theme" button to create one from scratch.
• A gallery of existing themes with a visual preview, each one labelled by scope: Company or Environment.
• Each theme has a radio button to apply it to this checkout and a "..." menu to edit it.

🧐 Themes are global: if you modify a theme, the change is applied automatically to every checkout using it. You can learn more about theme management in this guide.

Tab 4: Advanced settings

Technical settings of the checkout:

• Activate checkout: lets you disable it. The default checkout cannot be deactivated.
• Force MOTO option: enforces the MOTO option on all transactions processed through this checkout.
• Ignore SCA required error: ignores the strong authentication error if the bank requires it.
• Enforce in case of 3DS error: enforces the payment attempt even if 3DS authentication fails because of an outdated version.
• Recurring charges orchestration: lets you use a different orchestration for the recurring charges generated from payments in this checkout.

Live preview

The right panel shows a functional preview of the checkout in real time. You can control it along three axes:

• Operation type: Single Payment, Subscription or Authorization.
• Viewport: Desktop 🖥️ or Mobile 📱.
• Mode: Redirect (full view with the order summary) or iFrame (only the form, without the summary, for when you embed it in your own page).

You also have a zoom selector in the top right corner.

Publishing changes

Once the checkout is configured, click Publish in the top right. Until you publish, the changes are not applied to the checkout in production.

Practical use cases

Checkouts by currency

• EUR checkout → Segmentation: Currency Equal to EUR → Spanish methods (Bizum, Card via Redsys).
• USD checkout → Segmentation: Currency Equal to USD → international methods (Card via Stripe, PayPal).

Checkout with a unified theme

• In the Appearance tab, create a theme with your brand.
• Apply the same theme to every checkout of the merchant.
• If you update the theme, all checkouts inherit the changes automatically.

Updated on: 01/09/2026