| Tabla de Contenido |
|
|
Operational guide for configuring acquirer services, creating a Branch, and activating a merchant in the Kushki console.
1. Pre-requisite validations
To create a Kushki One merchant in the console you need:
- Access credentials with an Owner profile or with the necessary permissions to create merchants.
- Define whether the merchant will operate with a physical card (Card Present) or without a physical card (Card Not Present).
- The store address and the trade name (name that will appear on printed vouchers).
- The number of terminals the merchant will use at that point of sale.
- The email addresses to which the terminal activation codes will be sent.
2. Step 1: Create the Customer
The Customer is the operational configuration level. This is where payment processors, enabled payment methods, and rates that Branches will inherit (if centralized) are defined.
2.1 Start the creation
- Log in to the Kushki Console with Owner credentials.
- In the side menu, go to Customers and select the option to create a new Customer.
Side menu — Customers section in the Kushki Console
- Fill in the basic fields:
- Merchant name
- Customer type
- Country of operation, among others.
2.2 Customer Group (optional)
If the merchant belongs to a chain or group of branches that requires consolidated reporting, a Customer Group can be assigned at this step:
- Select an existing group from the list, or
- Type the name of a new one to create it instantly.
Animation: Customer Group assignment when creating a Customer
2.3 Configure the card processor
In the processors section, assign the corresponding card processor.
3. Step 2: Configure Acquirer Services
This is the new section that appears after the card processor when the merchant will operate with Kushki One. This is where how online or in-person payment operations will work is defined.
3.1 Operation type
Select whether the merchant will operate with:
- Card Present: the customer pays in person with their physical card at the terminal.
- Card Not Present: the merchant operates remotely or online.
If Card Not Present is selected, the section is complete here and no further fields appear.
If Card Present is selected, continue with the following fields.
3.2 Terminal type
Indicate whether the merchant will use:
- Kushki One terminals (Kushki SmartPOS): activates the complete Kushki One flow, including the generation of activation codes and configuration in the DMS.
- Own terminal (third-party device): in this case, the device provider section is activated to configure the integration keys.
3.3 Activation emails
If Kushki One terminals were selected, add the email addresses of the people who should receive the terminal activation codes.
- One or several emails separated by a comma can be entered.
- These emails are independent of the emails registered in the merchant's basic data.
- They can be updated or removed at any time from the Customer edit screen.
3.4 Payment options and payment types
Configure the transactional options that will be enabled for this merchant in the DMS:
- Available integration types (integrated / non-integrated).
- Enabled payment options (credit, debit, installments, etc.).
- Permitted payment types.
Once all fields are completed, save the section and proceed with the Branch creation.
Animation: Complete configuration of Acquirer Services
4. Step 3: Create the first Branch and activate the merchant
When the Customer form is completed and all sections are saved, the system will prompt you to create the first Branch. This action activates the merchant.
4.1 Branch fields for Kushki One
Unlike the traditional flow, when creating the first Branch of a Kushki One merchant three additional pieces of data are captured:
| Field | Description |
|---|---|
| Trade name | Name that will appear printed on the terminal vouchers (fantasy name or store name). |
| Merchant address | Exact physical address of the location where the terminals will operate. This address is also printed on the voucher. |
| Number of activation codes | Number of terminals this Branch will operate. Each terminal needs a unique activation code. |
4.2 What happens when you save the Branch?
When the Branch is created and the merchant users are configured, the system simultaneously:
- Activates the Customer and the Branch in the Console.
- Creates the merchant user for console access (same flow as always).
4.3 Welcome email with activation codes
Once the activation is processed, the merchant receives an email with its activation codes. The email includes:
- A welcome message and basic activation instructions.
- The activation code or codes (one per terminal). Each code is composed of the merchant's Merchant ID plus 6 randomly generated digits.
- Instructions on how to use the code on the terminal.
If the merchant has multiple terminals, the email lists all the codes or allows them to be downloaded as a file.
5. Adding additional Branches
If the merchant has more than one point of sale, repeat the Branch creation process for each location. Each additional Branch must have:
- Its own trade name and address (those that will appear on that location's vouchers).
- Its own number of activation codes (according to the number of terminals at that location).
6. Flow summary
| Step | Action | Result |
|---|---|---|
| 1 | Create Customer | The base operational configuration of the merchant is defined. |
| 2 | Assign Customer Group (optional) | The merchant is grouped for consolidated reporting. |
| 3 | Configure card processor | The Acquirer Services section is enabled. |
| 4 | Complete Acquirer Services | Operation type, terminals, emails, and payment options are defined. |
| 5 | Create first Branch | The merchant is activated and the name, address, and number of terminals are captured. |
| 6 | Configure merchant user | The merchant can log in to the console with their credentials. |
| 7 | Code generation (DMS) | Activation codes are created and sent to the merchant by email. |
| 8 | Create Customer or Customer Group report | The merchant begins receiving consolidated daily reports starting the following day at 3:00 a.m. |
Frequently Asked Questions (FAQ)
What happens if I enter the wrong number of activation codes?
If fewer codes than needed were configured, the support team can generate additional codes directly from the DMS without needing to modify the Branch. If more than needed were configured, the leftover codes will simply expire after 15 days without being used.
Is it possible to change the address or trade name after it has been created?
Yes. These details can be updated individually from the Branch edit screen, or in bulk using the CSV upload process from the Branches list. See the article 'How to bulk update Branches' for the bulk flow.
What emails should be entered in the Acquirer Services section?
They should be the emails of the people responsible for activating the terminals at the merchant: the store manager, the customer's IT manager, or the person who will physically install the devices. They do not need to be the same emails as the merchant's basic data.