Payment is a critical part of all Ecommerce solutions, and understanding the payment process is therefore important - here's a short description:

1. A customer adds products to their shopping cart, and then decides to check out.
2. During checkout she is asked to select a payment method - or perhaps a payment method is preselected and rendered inline in the shopping cart template.
3. A payment method uses a piece of software called a checkout handler to communicate with an external service called a payment provider - e.g. DIBS, QuickPay, Stripe, or PayPal - which presents the customer with a choice of cards and other methods used to actually pay.
4. The customer pays and the funds are reserved on the card.
5. Once the goods are dispatched - the payment is captured and relayed to the payment acquirer, which is typically a bank or an online wallet. 

In this document we describe how you create payment methods - if you want to jump directly to our checkout handler documentation go here.

To create a payment method:

• Go to Settings > Ecommerce > Orders > Payment
• Click New payment in the toolbar to open the payment method window (Figure 1.1)

A payment method consists of four sections:

• The Method section (1)
• The Country rates section (2)
• The Frontend Groups and Users section (3)
• The Fees section (4)
• The Cart type section (5)

The Method section is used to define the most basic properties – the name, a description, an icon.

The Countries section (Figure 2.1) is used to specify the country context for which this payment method should be available. 

Figure 2.1 Country rates

The country context is defined by the country set on the billing address of the user or visitor checking out – only the payment methods which have been made available for that country will be rendered. If you add states or regions to an ecommerce country they are also selectable here.

Only the payment methods created in the language set as the default language in the website Ecommerce settings will be rendered in frontend, so on a website with Danish set as the default ecommerce language, only the Danish payment methods are available (Figure 2.2). Of these payment methods, only the ones active for the billing country in the shopping cart are shown.

Figure 2.2 Payment methods available when Danish is the default ecommerce language for a website

The frontend groups and users section (Figure 3.1) is used to control which users or user groups will have access to this payment methods in frontend.

Figure 3.1 Use these settings to control who can see a payment method in frontend

Select All groups to make it available for everyone - and Selected groups to limit it to only a subset of your users. Check Anonymous users to make it available for anonymous users.

This section is often used on B2A solutions where you want to differentiate between consumers and business customers during checkout.

The Fees section (Figure 4.1) is used to create percentage-based or fixed-amount fees which will be added to the total price of an order when using this payment method.

Figure 4.1 Adding fees

To create a fee:

• Click Click here to add a new row
• Enter a fee and select a type – amount or percentage
• Select a Total Price at which point the fee will trigger – below this threshold, the fee will not trigger

As with other hierarchies, the more specific fee applies – a region fee trumps a country fee, and a country fee trumps an all countries fee. By default, fees are applied based on the billing country – but you can go to Settings > Ecommerce > Advanced Configuration and use the Fee Calculation setting to use the delivery country instead.

The Cart type section (Figure 5.1) is used to select a checkout handler for the payment method. A checkout handler is a piece of software which integrates with a payment provider such as PayPal or Stripe.

You can also select None and simply use the Fees section to charge an appropriate fee for shipping & handling.

Figure 5.1 Selecting a cart type

A checkout handler must be configured in accordance with the requirements of the payment provider – see the checkout handler documentation for details.