Merchant Console

user guide

Version 6.5 – February 2024

Introduction
This document describes the functionalities available in the merchant console of the payment
gateway platform and how to use it to achieve different tasks by using its interface. The purpose
of the document is to aid manual usage of the merchant console in performing different
configuration, account management, support etc. procedures using a web browser. The
document describes different procedures to achieve different tasks and expected results.

Change history record

Issue Description of Change Approval Date of Issue

1.0 Initial issue Emil Petkov 21/12/2011

2.0 All sections are updated with relevant information. Emil Petkov 29/04/2015

2.1 Added new sections – TC40, SAFE, Interchange Emil Petkov 12/10/2015
Rejects, Front End Rejects and new APMs
2.2 Added new screenshots due to gateway UI redesign, Emil Petkov 11/08/2016
added new risk filters and sections
2.3 Added description for IRF Report Emil Petkov 18/11/2016

2.4 Updated Dashboard page, API Documentation, Emil Petkov 23/12/2016

Payment Transactions page. Added SDD Refund,
Trustly Sale, Trustly Withdrawal, Interchange Details
pages.
2.5 Added SDD Payout, PayPal Express Checkout, Citadel Emil Petkov 15/05/2017
Payin, Citadel Payout, iDebit Payin, iDebit Payout,
InstaDebit Payin, InstaDebit Payout
2.6 Added Earthport, WeChat, Alipay, PaySec, PaySec Emil Petkov 11/09/2017
Payout.
New Customisable Columns feature.
Added new screenshots due to the new Gateway UI
changes.
Remove AVS as a transaction type.

Merchant Console User Guide 1

Version 6.5 – February 2024
2.7 Added RPN Payment, Intersolve, Fashioncheque, Emil Petkov 27/10/2017
TCS.
2.8 Updated the export information. Emil Petkov 07/12/2017

2.9 Added RPN Payout, Paycommerce, Neosurf, Klarna Emil Petkov 14/02/2018
Authorise, Klarna Capture, Klarna Refund and
Astropay Direct. Added Paycommerce Batches to the
Billing Section
3.0 Added Bancontact, QIWI, MyBank, GiroPay, Emil Petkov 16/04/2018
TrustPay, Zimpler, Safetypay, PayU, Instant Transfer,
Multibanco, iDEAL, EPS, Entercash, Pago 2ácil, PSE,
Rapipago, Link, Webpay, Carulla, Davivienda, Banco
de Chile, Surtimax, OXXO, Efecty, Argencard,
Naranja, Nativa, Cabal, Cencosud, Hipercard, Cartao
Mercado Livre, Elo, Aura, Astropay Card, Banamex,
Itau, Bradesco, Tarjeta Shopping, BBVA Bancomer,
Boleto Bancario, Redpagos, Santander, Santander
Cash, Baloto, EDEQ, Banco de Occidente, Banco do
Brasil.
3.1 Added new screenshots due to Gateway UI redesign. Emil Petkov 18/06/2018
Remove the Paybyvoucher yeepay payment method.
Change the name of Klarna Authorise to only Klarna.
3.2 Add Contract MCC based search criteria in the Emil Petkov 26/09/2018
Payment Transaction. Remove the Citadel Payin and
Citadel Payout payment methods.
3.3 Added Pay by link section under Virtual Terminal, Emil Petkov 11/04/2019
Updated Merchants Configuration section, Added
Consumers section, Updated payment transactions
3.4 New APMs and Transaction types have been added – Dimo Dilov 17/07/2019
Tola Sale, Tola Payout, eZeeCard Payout, BitPay Sale,
BitPay Payout, BitPay Refund. TransferTo Payout,
Incremental Authorise, Partial Reversal
3.5 Added new Specific Business Attributes for applicable Dimo Dilov 23/07/2019
merchants

3.6 New parameter for Virtual Terminal for Payout and Dimo Dilov 29/07/2019
Credit transactions has been implemented. Added new
search filter for payment transactions under specific
gateway
3.7 Updated Partial Reversal description, added FX Logs Dimo Dilov 12/08/2019
section to Payment Transactions

Merchant Console User Guide 2

Version 6.5 – February 2024
3.8 Changed name of method Tola Sale and Tola Payout Dimo Dilov 26/08/2019
for African Mobile Sale and African Mobile Payout

3.9 Added Email Templates configuration for Pay by link Dimo Dilov 17/09/2019
feature

4.0 Added description of the channels to send a Pay by Dimo Dilov 03/10/2019
link

4.1 Added description Email templates for Pay by link Dimo Dilov 24/10/2019
functionality. Fixed description of Blacklists and
Whitelists.
4.2 Added description of Card present new menus for ECP Dimo Dilov 13/11/2019

4.3 Added Token Sharing Group feature, removed Dimo Dilov 10/12/2019
Banamex and Entercash

4.4 New option “Supports Apple pay”, Update the Dimo Dilov 05/02/2020
Payment transaction section to reflect the new name of
the filter Transaction ID
4.5 New options to filter Stats and general improvements Dimo Dilov 28/03/2020

4.6 Shortening search field descriptions Dimo Dilov 30/06/2020

4.7 New Virtual Terminal UPI added, changed references Dimo Dilov 07/08/2020
to “Klarna” Virtual Terminal for “Invoice “and new
options and features to control the integration of the
merchants were added
4.8 Added new email configurations in merchants and Dimo Dilov 21/09/2020
terminals and new options for notifications

4.9 Added note about default timezone Dimo Dilov 21/10/2020

5.0 Added option Capture to the button Actions of a Dimo Dilov 27/01/2021
payment transaction

5.1 Added Issuing merchant configuration and the Dimo Dilov 04/03/2021
possibility to save custom payment transaction export
parameters

Merchant Console User Guide 3

Version 6.5 – February 2024
5.2 Added features to hide fields in WPF and description Dimo Dilov 06/04/2021
of Lightweight Virtual Terminal

5.3 Extended WPF options to hide optional fields Dimo Dilov 26/05/2021

5.4 Additional WPF options to hide optional fields Dimo Dilov 21/07/2021

5.5 Additional Card Present options for AMEX and ECP Dimo Dilov 08/09/2021
acquirers, added new WPF option and removed
disabled transaction types
5.6 Introduced new configurations with Apple Pay and Amir 25/11/2021
new features for merchant users
Fasihani

5.7 Introduced Managed recurring items, PIX, Russian Amir 17/01/2022

Mobile Sale and Russian Mobile Payout virtual
Fasihani
terminals
5.8 Added new merchant configurations and Ewallet, Anatoli 21/04/2022
Google Pay and Apple Pay virtual terminals
Tashev

5.9 Added new layout of WPF configuration Alejandro 02/08/2022

Salazar

6.0 Removed Trustpay from the list of virtual terminals. Alejandro 31/10/2022
Salazar

6.1 Added new parameter for bank payouts Alejandro 04/07/2022

Salazar

6.2 Updated creation of users with two factor Alejandro 30/10/2023

authentication
Salazar

6.3 Added Girocard to Card Present menu Alejandro 13/11/2023

Salazar

6.4 Added submenu Chargebacks to menu Risk Alejandro 01/12/2023

Management
Salazar

6.5 Added WPF Designer Alejandro 16/02/2024

Salazar

Merchant Console User Guide 4

Version 6.5 – February 2024
Merchant Console User Guide 5
Version 6.5 – February 2024
Table of contents
1. LOGIN AND ACCOUNT DETAILS ........................................................................................... 11

1.1. Logging into the gateway ........................................................................................................................................ 11

1.2. Preferences ............................................................................................................................................................... 14
1.3. Payment Transactions Custom export ................................................................................................................... 17
1.4. Default time zone ..................................................................................................................................................... 19
1.5. Reset your password ................................................................................................................................................ 19
1.6. Password requirements ........................................................................................................................................... 22
1.7. Logging out and Session timeout ............................................................................................................................ 22
1.8. Language preferences .............................................................................................................................................. 23
1.9. Dashboard index page ............................................................................................................................................. 23
1.10. Documentation ......................................................................................................................................................... 24

2. ANALYSIS ..................................................................................................................................... 25

2.1. Custom chart ............................................................................................................................................................ 25

2.2. All Terminals Report ............................................................................................................................................... 25
2.3. Stats ........................................................................................................................................................................... 26
2.4. Invoice ....................................................................................................................................................................... 28
2.5. IRF Report ............................................................................................................................................................... 29
2.6. Export Files .............................................................................................................................................................. 30

3. CONFIGURATION ....................................................................................................................... 30

3.1. Merchants ................................................................................................................................................................. 30

3.2. Web Payment Forms ............................................................................................................................................... 43
3.3. MIDs ......................................................................................................................................................................... 48

4. PAYMENT TRANSACTIONS ..................................................................................................... 50

4.1. Payment Transactions ............................................................................................................................................. 50

4.2. Processed Transactions ........................................................................................................................................... 54
4.3. Interchange Rejects ................................................................................................................................................. 54
4.4. Front End Rejects .................................................................................................................................................... 55
4.5. Transaction Notes .................................................................................................................................................... 56
4.6. Slow Transactions .................................................................................................................................................... 56
4.7. Transaction attempts ............................................................................................................................................... 57
4.8. Export Files .............................................................................................................................................................. 59

5. CARD PRESENT ........................................................................................................................... 60

5.1. AMEX ....................................................................................................................................................................... 60

Merchant Console User Guide 6

Version 6.5 – February 2024
5.2. Girocard ................................................................................................................................................................... 61
5.3. ECP ........................................................................................................................................................................... 61
5.4. Export files ............................................................................................................................................................... 66

6. WPF PAYMENTS ......................................................................................................................... 66

7. MANAGED RECURRING ITEMS ............................................................................................. 68

7.1. Managed recurring items details ............................................................................................................................ 68

7.2. Edit Managed rebilling item ................................................................................................................................... 69

8. CONSUMERS ................................................................................................................................ 71

8.1. Consumer details ..................................................................................................................................................... 72

9. VIRTUAL TERMINAL ................................................................................................................ 74

9.1. Authorize .................................................................................................................................................................. 76

9.2. Authorize3D ............................................................................................................................................................. 77
9.3. Capture ..................................................................................................................................................................... 79
9.4. Sale ............................................................................................................................................................................ 79
9.5. Sale3D ....................................................................................................................................................................... 80
9.6. Init recurring sale .................................................................................................................................................... 81
9.7. Init recurring sale3d ................................................................................................................................................ 81
9.8. Recurring sale .......................................................................................................................................................... 82
9.9. Account Verification ................................................................................................................................................ 82
9.10. Credit ........................................................................................................................................................................ 82
9.11. Payout ....................................................................................................................................................................... 83
9.12. eZeeCard Payout ..................................................................................................................................................... 85
9.13. Incremental Authorize ............................................................................................................................................ 85
9.14. Partial Reversal ........................................................................................................................................................ 86
9.15. CashU ........................................................................................................................................................................ 86
9.16. Paysafecard .............................................................................................................................................................. 87
9.17. eZeeWallet ................................................................................................................................................................ 87
9.18. Sofort......................................................................................................................................................................... 88
9.19. PPRO ........................................................................................................................................................................ 88
9.20. Neteller ...................................................................................................................................................................... 89
9.21. ABN iDeal ................................................................................................................................................................. 90
9.22. Webmoney ................................................................................................................................................................ 90
9.23. POLi .......................................................................................................................................................................... 91
9.24. Paybyvoucher sale.................................................................................................................................................... 91
9.25. SDD Sale ................................................................................................................................................................... 92
9.26. SDD Init Recurring Sale .......................................................................................................................................... 92

Merchant Console User Guide 7

Version 6.5 – February 2024
9.27. SDD Recurring Sale ................................................................................................................................................. 93
9.28. SDD Refund .............................................................................................................................................................. 93
9.29. Przelewy24 ................................................................................................................................................................ 93
9.30. SCT Payout............................................................................................................................................................... 94
9.31. Trustly Sale............................................................................................................................................................... 94
9.32. Trustly Withdrawal ................................................................................................................................................. 95
9.33. PayPal Express Checkout ....................................................................................................................................... 95
9.34. iDebit Payin .............................................................................................................................................................. 96
9.35. iDebit Payout ............................................................................................................................................................ 96
9.36. InstaDebit Payin....................................................................................................................................................... 97
9.37. InstaDebit Payout .................................................................................................................................................... 97
9.38. Earthport .................................................................................................................................................................. 98
9.39. WeChat Pay .............................................................................................................................................................. 98
9.40. Alipay ........................................................................................................................................................................ 99
9.41. Online Banking ........................................................................................................................................................ 99
9.42. Bank Payout ........................................................................................................................................................... 100
9.43. RPN Payout ............................................................................................................................................................ 100
9.44. Intersolve ................................................................................................................................................................ 100
9.45. Fashioncheque ........................................................................................................................................................ 101
9.46. The Container Store (TCS) ................................................................................................................................... 101
9.47. Paycommerce ......................................................................................................................................................... 101
9.48. Neosurf .................................................................................................................................................................... 102
9.49. TransferTo Payout ................................................................................................................................................. 102
9.50. UPI .......................................................................................................................................................................... 103
9.51. Invoice ..................................................................................................................................................................... 104
9.52. Invoice Capture ...................................................................................................................................................... 105
9.53. Invoice Refund ....................................................................................................................................................... 106
9.54. BitPay ...................................................................................................................................................................... 107
9.55. BitPay Payout ......................................................................................................................................................... 108
9.56. BitPay Refund ........................................................................................................................................................ 109
9.57. African Mobile Sale ............................................................................................................................................... 109
9.58. African Mobile Payout .......................................................................................................................................... 110
9.59. Astropay Direct ...................................................................................................................................................... 111
9.60. Bancontact .............................................................................................................................................................. 112
9.61. QIWI ....................................................................................................................................................................... 112
9.62. MyBank .................................................................................................................................................................. 113
9.63. Giropay ................................................................................................................................................................... 113
9.64. Zimpler ................................................................................................................................................................... 114
9.65. Safetypay ................................................................................................................................................................ 114

Merchant Console User Guide 8

Version 6.5 – February 2024
9.66. PayU ........................................................................................................................................................................ 115
9.67. Instant Transfer ..................................................................................................................................................... 115
9.68. Multibanco.............................................................................................................................................................. 116
9.69. iDEAL ..................................................................................................................................................................... 116
9.70. EPS .......................................................................................................................................................................... 116
9.71. Pago Facil ............................................................................................................................................................... 117
9.72. PSE .......................................................................................................................................................................... 117
9.73. Rapipago ................................................................................................................................................................. 118
9.74. WebPay ................................................................................................................................................................... 118
9.75. Carulla .................................................................................................................................................................... 119
9.76. Davivienda .............................................................................................................................................................. 119
9.77. Surtimax ................................................................................................................................................................. 120
9.78. OXXO ..................................................................................................................................................................... 121
9.79. Efecty ...................................................................................................................................................................... 121
9.80. Argencard ............................................................................................................................................................... 122
9.81. Naranja ................................................................................................................................................................... 122
9.82. Nativa ...................................................................................................................................................................... 123
9.83. Cabal ....................................................................................................................................................................... 123
9.84. Cencosud ................................................................................................................................................................. 124
9.85. Hipercard................................................................................................................................................................ 124
9.86. Elo ........................................................................................................................................................................... 125
9.87. Aura ........................................................................................................................................................................ 125
9.88. Astropay Card ........................................................................................................................................................ 126
9.89. Banco Itaú............................................................................................................................................................... 126
9.90. Bradesco ................................................................................................................................................................. 127
9.91. Tarjeta Shopping ................................................................................................................................................... 127
9.92. BBVA Bancomer .................................................................................................................................................... 128
9.93. Boleto Bancario ...................................................................................................................................................... 128
9.94. Redpagos................................................................................................................................................................. 129
9.95. Santander................................................................................................................................................................ 129
9.96. Santander Cash ...................................................................................................................................................... 130
9.97. Baloto ...................................................................................................................................................................... 130
9.98. Empresa de Energia............................................................................................................................................... 131
9.99. Banco de Occidente ................................................................................................................................................ 131
9.100. Banco do Brasil ...................................................................................................................................................... 132
9.101. Refund..................................................................................................................................................................... 133
9.102. Void ......................................................................................................................................................................... 133
9.103. Apple Pay ................................................................................................................................................................ 133
9.104. Pay By Link ............................................................................................................................................................ 134

Merchant Console User Guide 9

Version 6.5 – February 2024
9.105. Google Pay .............................................................................................................................................................. 138
9.106. Russian Mobile Sale ............................................................................................................................................... 138
9.107. Russian Mobile Payout .......................................................................................................................................... 139
9.108. Pix ............................................................................................................................................................................ 139
9.109. eWallet .................................................................................................................................................................... 140

10. BLACKLISTS .............................................................................................................................. 141

10.1. Blacklists ................................................................................................................................................................. 141

10.2. Add Entries............................................................................................................................................................. 142
10.3. Stats ......................................................................................................................................................................... 143
10.4. Imports ................................................................................................................................................................... 144
10.5. Export Files ............................................................................................................................................................ 145

11. WHITELISTS .............................................................................................................................. 145

11.1. Whitelists ................................................................................................................................................................ 145

11.2. Add Entries............................................................................................................................................................. 147
11.3. Stats ......................................................................................................................................................................... 147
11.4. Imports ................................................................................................................................................................... 148
11.5. Export Files ............................................................................................................................................................ 149

12. RISK MANAGEMENT ............................................................................................................... 149

12.1. Chargebacks ........................................................................................................................................................... 149

12.2. Retrieval Requests ................................................................................................................................................. 150
12.3. SAFE ....................................................................................................................................................................... 151
12.4. TC40 ........................................................................................................................................................................ 152
12.5. Export files ............................................................................................................................................................. 153

13. BILLING....................................................................................................................................... 153

13.1. Interchange Details ................................................................................................................................................ 153

13.2. Paycommerce Batches ........................................................................................................................................... 154
13.3. Export Files ............................................................................................................................................................ 154

14. USERS ........................................................................................................................................... 154

Merchant Console User Guide 10

Version 6.5 – February 2024
1. Login and account details

You will be provided with login credentials via email with further instructions and steps
you should follow. To log into Genesis, you need to have the following details:

• Username
• Password (to be configured by the user upon account activation)
• Dedicated URL for access to the Merchant Console of the Genesis gateway.

1.1. Logging into the gateway

Open your browser and go to the URL provided in the activation email.
Enter your username and password in the relevant fields, then click on the button “Log
in”.
Note: Both, the username and the password are case sensitive and must be entered
exactly as provided/created.

Merchant Console User Guide 11

Version 6.5 – February 2024
You can change the language of the application from the top right corner of the page by
selecting the preferred language from the dropdown list.

Successful login
Depends on your access role, if you have authenticated successfully, you will be
redirected either to the Dashboard’s index page or directly to the Virtual Terminal
(lightweight merchant console) as shown below.

Merchant Console User Guide 12

Version 6.5 – February 2024
Light Merchant console:

Failing to log in
If on the login attempt you have received an error message Login failed., this means that
you are mistaking either the username or the password. Make sure that you’re using the
correct username and password, if you are still unable to log in, please follow the
described steps to reset your password in section 1.3. Reset your password.

Merchant Console User Guide 13

Version 6.5 – February 2024
If you have received the following error message due to multiple login failures:
Login failed. Account disabled, too many failed logins, Please contact support.
Please contact the Tech Support team at [email protected] to enable
your account.
If you have received the following error message:
Account disabled, Please contact support.
Your account has been disabled due to inactivity, so please contact the Tech Support
team at [email protected] to enable your account.

1.2. Preferences

The button Preferences is placed on the top right corner of your screen and there
are two options:

- Update user - if you want to change your password, please use this option. The
following page will open, where you will be prompted to enter your current
password and the new one:

Merchant Console User Guide 14

Version 6.5 – February 2024
 - Customisable Columns – this option allows you to choose which columns to be
visible on the following sections: Payment Transactions; Processed Transactions;
Chargebacks; Card Present ECP; Retrieval Requests; SAFE; TC40.

Merchant Console User Guide 15

Version 6.5 – February 2024
Merchant Console User Guide 16
Version 6.5 – February 2024
1.3. Payment Transactions Custom export

- Customisable columns for the user. You can select specific columns to be
exported for the Payment Transactions.

*Note: User selected fields in the Custom Exports are now saved until changed by the
merchant and/or Genesis User and are not session related.

Merchant Console User Guide 17

Version 6.5 – February 2024
Merchant Console User Guide 18
Version 6.5 – February 2024
1.4. Default time zone

Currently, Genesis uses UTC as the default time zone. At this time, this preference
cannot be changed. The user must take this into account when performing any kind of
search.

1.5. Reset your password

From the login page

To reset your password please open the gateway URL provided to you in the activation
email. Make sure you are on the login page and click on the link can’t login? placed
below the username and password fields.

Merchant Console User Guide 19

Version 6.5 – February 2024
You will be redirected to a page where you need to provide the login username and the
email address of the user account.

Once you have entered the required information in the fields, please click on the button
Submit.
An email will be sent to the mailbox registered for that account containing one-time link
for password reset. When you click on it, the following page will open:

Merchant Console User Guide 20

Version 6.5 – February 2024
You need to enter your new password and it should comply with the password
requirements listed in section 1.4. Password requirements.
From the gateway user interface
Once you have logged in if you want to change your password, please click on the button
Preferences in the top right corner of the window.

The following page will open where you will be prompted to enter your current password
and the new one:

Merchant Console User Guide 21

Version 6.5 – February 2024
1.6. Password requirements

The following requirements should be fulfilled when you set your password:

• Password must be at least nine characters.

• Must contain a lowercase letter, an uppercase letter and a digit.
• Must be different from the last four passwords you've used.
• Expires every 45 days automatically.
• Note that the account is locked out after five wrong password attempts.

1.7. Logging out and Session timeout

Due to security reasons, it is recommended to log out from the gateway when you have
finished with all your tasks.

Merchant Console User Guide 22

Version 6.5 – February 2024
The gateway will automatically log you out after 15 minutes of inactivity. You can see
when your session will expire by looking at the countdown in the top right corner of your
screen, as shown below:

1.8. Language preferences

The language of the application can be changed from the dropdown list placed in the top
right corner of the window. Once the desired language is chosen, all labels in the
application will be changed automatically.

1.9. Dashboard index page

Genesis dashboard provides visual charts, enabling quick insights into real-time data. It
gives you the ability to observe the daily volumes converted into a different currencies
such as USD, EUR, GBP etc., see the top five terminals and merchants based on the
processing volume passed through them, to check the processing health and the
chargeback/fraud ratios.

Merchant Console User Guide 23

Version 6.5 – February 2024
1.10. Documentation

After successful login, on the left panel menu, navigate to the bottom of the menu and
click “Downloads”.

• The API documentation can be found and downloaded from the main left menu
under “Downloads” at the very bottom of it. It is always automatically generated
and is the latest version of the API. This document is intended for technical
people.
• Online API Documentation contains Slate API Documentation and is accessible
online.
• The User Guide documentation can be found and downloaded from the main left
menu under “Downloads” at the very bottom of it. It is always automatically
generated and is the latest version of the User Guide. This document describes the

Merchant Console User Guide 24

Version 6.5 – February 2024
 functionalities available in the admin console of the payment gateway platform
and how to use it to achieve different tasks by using its interface.

2. Analysis

With all the retail transactions being passed through the Genesis payment gateway, you
can view detailed reports, as well as graphs and charts of all transactions since the
account’s existence.
The Analysis tool provides the option to run the following types of reports: Custom
Chart, All Channels Report and Invoices. For ‘All Terminal Report’, ‘Stats’, ‘IRF
Report’ and ‘Invoice’, reports can also be exported to CSV and Excel files.

2.1. Custom chart

You need to select the required field and choose from the following options: Show graph,
Show deltas.

2.2. All Terminals Report

You need to select the required fields and click on “Generate CSV” or “Generate Excel”:

Also, you have the following predefined options to retrieve reports that you can choose to
automatically generate and export these:

Merchant Console User Guide 25

Version 6.5 – February 2024
 • Last and previous week CSV
• Last and previous week Excel
• Last and previous month CSV
• Last and previous month Excel

2.3. Stats

In this section, you can retrieve statistical reports for merchant terminals and MIDs, and
thereafter export these into CSV or Excel file formats.

Stats by Terminal
You need to select a date range and a merchant. If you choose the option “Split per card
brand”, it will split the volume reports per card brand. If you choose the option “Only
processing”, it will split reports per processing volume of terminals. Once you retrieve
the data, you can export it in CSV or Excel file formats and preview it in a chart. You
will see the volume and the ratios separated per terminal.

Merchant Console User Guide 26

Version 6.5 – February 2024
Stats by MID
You need to select a date range and a merchant. There are three options available.

- “Split per card brand” will split the volume reports per card brands.
- “Only processing” will split reports per processing volume of MIDs.
- “Split by currency” will split the volume reports per currencies.

Once you retrieve the data, you can export it in CSV or Excel file formats and preview it
in a chart. You will see the volume and the ratios separated per MIDs.

Merchant Console User Guide 27

Version 6.5 – February 2024
2.4. Invoice

In this section, you can generate invoices for terminals, MIDs and merchants, and
thereafter export these into CSV or Excel file formats.

Invoice by Terminal
You need to select the terminal, month, and week, or choose Custom Date Range. Then,
you can generate a CSV or Excel file by clicking on the relevant buttons.

Invoice by MID

Merchant Console User Guide 28

Version 6.5 – February 2024
You need to select the MID, month, and week, or choose Custom Date Range. Then, you
can generate a CSV or Excel file by clicking on the relevant buttons.

Invoice by Merchant
You need to select the Merchant, month, and week, or choose Custom Date Range. Then,
you can generate a CSV or Excel file by clicking on the relevant buttons.

2.5. IRF Report

IRF Report is automatically generated based on imported interchange details and

processed transactions. Search section can be used to filter the IRF reports. Both CSV
and Excel export is available.

Merchant Console User Guide 29

Version 6.5 – February 2024
 2.6. Export Files

From this tab, you can find and download any CSV or Excel exports you have made
previously, so you do not have to re-generate and export them again.

3. Configuration

To set up merchant and associated MIDs we can use the Merchant Configuration tool as
described below. In order to reach the Configuration tab, you need to log in as a merchant
user by using the merchant URL with the right administrative privileges and simply
clicking on the Configuration tab.

3.1. Merchants

The Merchants tab provides a view of the merchant that the admin is assigned to:

If we want to see what details our merchant contains, we can click on the “Actions”
button ( ) and then on the “View Details” button ( ), where all the
information for the particular merchant will be shown.

Merchant Console User Guide 30

Version 6.5 – February 2024
From here, we can also view our MIDs by clicking on the “MIDs” dropdown ( )and
Terminals by clicking on the “Terminals” dropdown ( ). The system will show all
MIDs/Terminals which are set for the merchant.
The section “Token Sharing group” is not editable. However if you click on it, you will
see if the merchant is part of any Token Sharing group. This feature enables merchants
and/or resellers that belong to the same group to process transactions with a shared token
that contains cardholder data.

Merchant Console User Guide 31

Version 6.5 – February 2024
If you click on the “Terminals” button ( ), you will be able to see all terminals
linked to this particular merchant.

If we want to see what details a particular terminal contains, we can click on the
“Actions” button ( ) and then on the “View Details” button ( ).
Here we can see information such as Terminal Token, Supported Features, Supported
Transaction types, Filters, API Access details, and even the Decline Reasons for the last
month for this terminal.

Merchant Console User Guide 32

Version 6.5 – February 2024
Merchant Console User Guide 33
Version 6.5 – February 2024
Terminal Email Configuration

In order to have an active Mailer service for the merchant’s clients, you need to use
Email Configuration on Terminal Level.

You will be able to add new emails by clicking on or

the existing ones.

Configure new Email Configuration:

You can select Type, Name and Recipients and Save your Email Configuration.

- Type: can be selected from the dropdown menu, they are grouped as
“TRANSACTION EMAILS”.
- Name: you can choose any names.
- Recipients: The recipients’ field can be configured in cases when a custom
recipient is required. If it is not configured, it will send the mail to the
Merchant User.

Email Templates
Merchants have the option to use the default email templates or use the customisable
ones.

Merchant Console User Guide 34

Version 6.5 – February 2024
By editing any customisable emails, you will be able to Configure a new Email
Template.

Clicking the button “Configure new Email Template” will open an editor that will allow
you to customise several aspects of the email:

• Subject
• Language
• Body

Once you enter the desired template subject and select the template language (the

language can be also set as the default one ), the body of the template can
be enhanced with the use of variables that will make it more dynamic by including
information related to the cardholder. The use of variables is optional, but they allow to
personalise the content by embedding the following information: First and Last name of
the cardholder, Address, Zip Code, State, Country, a link to the payment form that the
cardholder can open to finish the payment, the amount with currency and type of
transaction.

Merchant Console User Guide 35

Version 6.5 – February 2024
If there are already some templates created, then you can edit them by choosing them
from the “Actions”.

If no template is defined, the system will send a default one with a link for the cardholder
to go to the payment form and finalise the transaction.

Merchant Console User Guide 36

Version 6.5 – February 2024
3.1.1 Pay Later Reminder Settings
‘Pay Later’ is added for the merchant as a supported feature for the Web Payment Form
(WPF) and in the Virtual Terminal for Pay By Link. The option is available for Editing

in the top right corner of the Merchant Details page under

Reminder Configuration

- Up to three reminders can be configured for each payment.

- The available methods for sending reminders are email and SMS.
- The time for sending a reminder is set in number of minutes after payment creation.
- The time for sending each reminder should not be greater than the configured
payment lifetime.

As soon as changes have been applied to the option Pay Later, its settings will appear in
the Merchant Details section on the right side of the page:

Merchant Console User Guide 37

Version 6.5 – February 2024
For configuration options or any other additional questions, you can always contact Tech
Support at [email protected]

3.1.2 Email Configuration

In order to have an active Mailer service, you need to use Email Configuration.

You will be able to add new emails by clicking on or

the existing ones.

Configure new Email Configuration:

Merchant Console User Guide 38

Version 6.5 – February 2024
You can select Type, Name and Recipients and Save your Email Configuration.

- Type: can be selected from the dropdown menu, they are grouped as
“TRANSACTION EMAILS”, “GENERAL EMAILS” and “REMINDER
EMAILS”.
- Name: you can choose any names.
- Recipients: The recipients’ field can be configured in cases when a custom
recipient is required. If it is not configured, it will send the mail to the
Merchant User.

Email Templates
Merchants have the option to use the default email templates or using the customisable
ones.
By editing any customisable emails, you will be able to Configure a new Email
Template.

Clicking the button “Configure new Email Template” will open an editor that will allow
you to customise several aspects of the email:

• Subject
• Language
• Body

Merchant Console User Guide 39

Version 6.5 – February 2024
Once you enter the desired template subject and select the template language (the

language can be also set as the default one ), the body of the template can
be enhanced with the use of variables that will make it more dynamic by including
information related to the cardholder. The use of variables is optional, but they allow to
personalise the content by embedding the following information: First and Last name of
the cardholder, Address, Zip Code, State, Country, a link to the payment form that the
cardholder can open to finish the payment, the amount with currency and type of
transaction.

Merchant Console User Guide 40

Version 6.5 – February 2024
If there are already some templates created, then you can edit them by choosing them
from the “Actions”.

If no template is defined, the system will send a default one with a link for the cardholder
to go to the payment form and finalise the transaction.

Apple Pay Onboarding

• Payment Processing Certificates

Merchant Console User Guide 41

Version 6.5 – February 2024
In order to use the Apple Pay integration, the merchant is required to upload or provide a
Payment Processing Certificate (.p12) file. There are three ways to generate the required
certificate:

• OpenSSL
• KeyTool
• Keychain Access (Mac only)

Instructions on how to generate the certificate can be found under each of the methods to
generate it after you click on the arrow icon ( ).

• Direct Registration

Allows the Merchant URL(s) to be entered and sent for validation through the Apple
Merchant Registration API.

The "Download Validation File" button calls the Merchant Registration API and once a
domain validation file is obtained in response, it is downloaded locally on the user's
machine.

Merchant Console User Guide 42

Version 6.5 – February 2024
3.2. Web Payment Forms

The WPF (Web Payment Form) is a customisable component of Genesis and offers the
opportunity for numerous payment methods through a payment page facilitated by
Genesis.
If the Web Payment Form is enabled, you can select an existing WPF configuration.

When selected, it navigates to the Edit menu, containing the following parameters:

• Show WPF Fields - Provide the ability to select which of the following
options/fields to be displayed on the Web Payment Form.

Merchant Console User Guide 43

Version 6.5 – February 2024
 • WPF Top Level Bank Codes - When the user selects one of the bank
methods under "Online Banking", the "Country" dropdown list suggests
only countries where this bank is supported.

• Logo – Add a custom merchant logo. The merchant account must have
Show merchant logo enabled.

Merchant Console User Guide 44

Version 6.5 – February 2024
 • Terms & Policy Template – The merchant can have their custom Terms
and Policy. The merchant account must have Show merchant terms and
policy template enabled.

• Terms & Conditions – The merchant can have their custom Terms and
Conditions. The merchant account must have Show merchant terms and
conditions enabled.

• Privacy Policy – dropdown menu from where optionally you can upload
Privacy Policy for the merchant. The merchant account must have Show
merchant privacy policy enabled.

• Custom WPF CSS – allowing the merchant

- to upload .css file to customise the WPF or;
- to choose from our predefined Themes (the Dark theme is by default)

Merchant Console User Guide 45

Version 6.5 – February 2024
 - to customise the styling

The last introduced "Custom" option gives you choices for setting the colours of
the separate areas in the Web Payment Form.

In this way, the uploading of a .css file for approval becomes almost unnecessary.

Merchant Console User Guide 46

Version 6.5 – February 2024
The image below demonstrates the different areas/components, that may be
customised:

In the WPF life styling panel, you may also

- Zoom in and out
- Change the theme to Dark/Light

• WPF Designer – allows merchants to customize the way the WPF form looks
▪ You can choose to customize:
- Colours and background – theme (light/dark), brand colour,
background colour, a choice to have a background image and upload
one, layout position

Merchant Console User Guide 47

Version 6.5 – February 2024
 - Font
- Shapes – input size and corner radius
The image below showcases the entire customizable WPF Designer:

•
WPF Custom Footer text – allowing the merchant to provide a footer
with the wording they would like to be displayed in the form. The footer
text must be sent to Tech Support for configuration in the form.

• WPF Purchase Summary – allowing the merchant to change the wording

of the top banner that summarises what the customer will be paying for.
The purchase summary text must be sent to Tech Support for configuration
in the form.
3.3. MIDs

The MIDs tab only provides us with a view of all MIDs:

From here, we can see the MID with the assigned terminals, which are the enabled
currencies, and the enabled card brands for the MIDs.

Merchant Console User Guide 48

Version 6.5 – February 2024
By clicking on the “Actions” button ( ) and then on the “View Details” button
( ), the system will display the Show MID page, from where we can find more
details on how this MID was configured, information such as Merchant Identification
Number (MID), Supported Features, Supported transaction types, enabled currencies,
enabled cards brands, and assigned terminals among others.

Merchant Console User Guide 49

Version 6.5 – February 2024
4. Payment Transactions

4.1. Payment Transactions

From this tab, you can find a particular transaction or a group of transactions by using
different search criteria:

• Merchant Transaction ID
• Unique ID
• Date range From – To: Searchable by year, month, days, hours, minutes and
seconds.

Merchant Console User Guide 50

Version 6.5 – February 2024
 • By payment days
• Merchant
• You can also add additional search criteria: Reseller subtype, Acquirer, Card
Holder, Card No. (last four digits), Card Bin. (first six digits), Email, Type, and
Status, among others.

Once you have retrieved the information you are searching for, you have the option to
export it in CSV or Excel file formats.

• If you want to customise the export, you can click on the “Export Files” button (
) and select “Custom Export” ( ). The available columns to
export are: Status; Created At; Merchant name; Terminal; Type; Error class;
Merchant transaction ID; among others.

Merchant Console User Guide 51

Version 6.5 – February 2024
 o You will be able to export the customised file in CSV format or
Excel , also by using the “Save preferences” button
you are able to Save your customised report for future use.

If you click on the Volumes for selection’s “Show” button the below table will be shown
where you can choose to view the information separated per currency (from the
dropdown list).

If you want to check if a particular payment transaction has been cleared successfully

with the 80byte can open it by clicking on the “Actions” button ( ) and then
clicking on the “View Details” button ( ) and see if there is a processed
transaction related to it. Also, once you open a transaction you can see all the processing
logs. You can refund ( ) or void ( ) a transaction directly
from here.

Merchant Console User Guide 52

Version 6.5 – February 2024
 • The “view details” option appears when clicking on the Actions button.

When opening the transaction details, the following new fields appear:

- Transaction Notes
- Log
- MID Reconciliation log
- FX Logs
- Risk Details
- Billing address
- Details
- Notification
- Additional Attributes
- Consumer

If you want to Capture only an Authorize/Authorize3D transaction directly from the menu, you

can do it by clicking the “Actions” ( ) button and then clicking on the button Capture (
). This will forward you to the Capture Transaction type form of the Virtual Terminal
with pre-populated values from the Authorize Transaction that you select for capturing.

Merchant Console User Guide 53

Version 6.5 – February 2024
4.2. Processed Transactions

Here you can find all processed (cleared) transactions with Omnipay. You can retrieve
the ARNs from here if requested by a merchant or internally.

You can search by:

• ARN
• Merchant
• Transaction date range From – To
• Filter - Reseller subtype

4.3. Interchange Rejects

Here you can find Interchange Rejects with Omnipay.

Merchant Console User Guide 54

Version 6.5 – February 2024
You can search by:

• ARN
• Merchant
• Reject Type
• Codes
• Transaction date range From – To
• Filter - Reseller subtype

4.4. Front End Rejects

Here you can find Front End Rejects with Omnipay.

Merchant Console User Guide 55

Version 6.5 – February 2024
You can search by:

• ARN
• Merchant
• Status
• Transaction date range From – To
• Filter - Reseller subtype

4.5. Transaction Notes

Here you can find different events that occurred for specific transactions, such as:
Chargebacks, Fraud reports, Retrieval requests, comments/notes, etc. You have the
following search options: “Date range”, “Merchants”, “Category”, “Priority and
“Reviewed”:

If you want to open the transaction for which is a note click on the “Actions” button (

) and then click on the “View Details” button ( ), to delete a note

click on the “Delete note” button ( ).

4.6. Slow Transactions

From here, you can find which transactions have been processed slower than usual. You
need to choose the required fields and click on the “Search” button.

Merchant Console User Guide 56

Version 6.5 – February 2024
Search options:

• Transaction ID
• Merchant
• Date range From – To
• By payment days
• You can also add additional search criteria: Reseller subtype, Acquirer, Card
Holder, Card No. (last four digits), Card Bin. (first six digits), Email, Type, and
Status, among others.

4.7. Transaction attempts

By using this tool, you can monitor for any issues that you might have with the
transactions posted to our gateway. If the Merchant and Terminal columns are empty,
this means that you have failed to authenticate via the API and therefore the request is
recorded without an owner.

Search options:

• Merchant

Merchant Console User Guide 57

Version 6.5 – February 2024
 • Date range From – To
• You can also add additional search criteria: Terminal, IP Address, Error
Message, Raw Request

If you want to open a particular record to view the full information for it, click on the

“Actions” button ( ) and then click on the “View Details” button

( ), then the following information will be shown:

Merchant Console User Guide 58

Version 6.5 – February 2024
4.8. Export Files

From this tab, you can find and download any CSV or Excel exports you have previously
made, so you do not have to re-generate and export them again.

Merchant Console User Guide 59

Version 6.5 – February 2024
5. Card Present

5.1. AMEX

In this tab, you can search for card present transactions that were processed via the
AMEX acquirer. You can export the results into CSV and Excel files.

Search options:
• Merchants
• Date range From – To
• You can also add additional search criteria: Merchant number and Terminal.

Merchant Console User Guide 60

Version 6.5 – February 2024
5.2. Girocard

In this tab, you can search for card present transactions that were processed via the
Girocard acquirer. You can export the results into CSV and Excel files.

Search options:
• Merchants
• Date range From – To
• You can also add additional search criteria: Merchant number and Terminal.

5.3. ECP

5.2.1 Recent Authorizations: This functionality allows admin and

reseller/merchant users to see Card Present Transactions Recently Authorized via the
ECP acquirer. You can customise the column and export the results into CSV and Excel
files.

Search options:

• Auth Code

Merchant Console User Guide 61

Version 6.5 – February 2024
 • Merchants
• Authorisation date
• Reseller subtype
• Merchant number

5.2.2 Authorizations: This functionality allows admin and reseller/merchant users

to see Card Present data that has been Authorised via the ECP acquirer. You can
customise the column and export the results into CSV and Excel files.

Search options:

• ARN
• Merchants
• Date range From - To
• You can also add additional search criteria: Reseller subtype
• Customisable Columns: Created At, authorisation date, merchant number, amount,
among others.

5.2.3 Chargebacks: This functionality allows admin and reseller/merchant users

to see Card Present chargeback data via the ECP acquirer. You can customise the column
and export the results into CSV and Excel files.

Merchant Console User Guide 62

Version 6.5 – February 2024
Search options:

• ARN
• Merchants
• Date range From - To
• You can also add additional search criteria: Reseller subtype

Customisable Columns: Created at, Original Transaction Date, Merchant Name,

and Item type, among others.

5.2.4 Rapid Dispute Resolutions: This functionality allows admin and

reseller/merchants users to see all Rapid Dispute Resolutions related to the ECP
acquirer. You can customise the column and export the results into CSV and Excel files.

Search options:

• ARN
• Merchants
• Original transaction date

Merchant Console User Guide 63

Version 6.5 – February 2024
 • Reseller subtype
• Auth Code
• Merchant Reference Transaction
• Reason Code

5.2.5 Interchange Details: This functionality allows admin and reseller/merchant

users to see the Interchange Details related to the ECP acquirer. You can customise the
column and export the results into CSV and Excel files.

Search options:

• Item Number
• Merchants
• Post date
• Reseller subtype
• Merchant Number
• Merchant Reference Transaction

5.2.6 Processed Transactions: This functionality allows admin and

reseller/merchant users to see Card Present data that has been processed via the ECP
acquirer. You can customise the column and export the results into CSV and Excel files.

Merchant Console User Guide 64

Version 6.5 – February 2024
Search options:

• ARN
• Merchants
• Date range From - To
• You can also add additional search criteria: Reseller subtype, Terminal ID and
Merchant Number
Since some merchants have more than one POS terminal and location which are
connected to the same MID, searching under the Terminal ID allows
distinguishing the reporting for the different devices.

• Customisable Columns: Created at, Transaction date, Merchant, Transaction type,

among others.

Merchant Console User Guide 65

Version 6.5 – February 2024
 5.2.7 Retrieval Requests: This functionality allows admin and reseller/merchant
users to see Card Present retrieval request data via the ECP acquirer. You can customise
the column and export the results into CSV and Excel files.

Search options:

• ARN
• Merchants
• Date range From - To
• You can also add additional search criteria: Reseller subtype

Customisable Columns: Created at, Original Transaction Date, Merchant Name, and
Reason Code, among others.

5.4. Export files

From this tab, you can find and download any CSV or Excel exports of Card Present data
you have made previously, so you do not have to re-generate and export them again.

6. WPF Payments

This functionality shows all payments made through the Web Payment Form (WPF) by
the merchant.

Merchant Console User Guide 66

Version 6.5 – February 2024
For more information on a particular WPF payment click on the “Actions” button and
then on the “View Details” button ( ). The following information will be shown:

• WPF Payment

• Payment Transactions – in this section you will see all transactions related to a
particular WPF payment.

You have the Actions button with the following actions:

- View Details
- Refund transaction
- Reconcile transaction
- Add to blacklist

Merchant Console User Guide 67

Version 6.5 – February 2024
 • Logs – dropdown menu from where you can see the incoming request, the
incoming payment form request params and whether a notification was created or
not.
• Billing Address – dropdown menu with the customer billing address for a
particular WPF payment.
• Details – dropdown menu with all details related to a WPF payment.
• Notification – dropdown menu which shows information about the notification
like when it is created, its status, etc.

7. Managed Recurring Items

This menu allows the merchant to control the recurring payment schedule. These
payments will be triggered automatically by the gateway following the instructions and
configurations entered by the merchant when the recurring item is created.

7.1. Managed recurring items details

Merchant Console User Guide 68

Version 6.5 – February 2024
The Actions button allows you to see different options to perform on a managed rebilling
item:

When the View Details option is selected, a summary of the item will be displayed:

7.2. Edit Managed rebilling item

This form allows the merchant to edit the conditions and configuration of a managed
recurring item, allowing them total control over the schedule of the subsequent payments.

Merchant Console User Guide 69

Version 6.5 – February 2024
The fields of the form are the following:

- Amount that will be charged on each subsequent payment.

- Interval type for the recurring payment. Possible values are days or months.
- Number of periods in days or months. Values range from 1 to 30 if the interval
was days and 1 to 12 if it was months.
- Maximum number of times (Max count) that this payment will occur. Leave
empty for unlimited recurring.
- The UTC hour in the day for the execution of the recurring transaction, default
value 0.
- Status of the recurring item. Possible values are active or suspended.

Merchant Console User Guide 70

Version 6.5 – February 2024
 - Next date on which the recurring payment will start to run.
- A comment for when the recurring item is cancelled.

8. Consumers

The Consumers menu has the purpose of searching for customers (consumers) based on
specific conditions and parameters, and then viewing and editing certain properties and
specs. Once a consumer is found, one can display all the details and all the transactions of
the consumer. More information about the purpose of the consumer can be found in the
API documentation.
The search is currently based on the following parameters:

- Date range – searches for the customers who were active in a specific period.
- Merchant – If a specific merchant owns several different merchant accounts, they
can select the account of interest. If only one account is available, it will
automatically appear in the dropdown field.
- Consumer ID – A limited range of consumers can be displayed based on parts of
their ID.
- Email - A limited range of consumers can be displayed based on parts of their
email address.

Merchant Console User Guide 71

Version 6.5 – February 2024
 - Status - It can be looked exclusively for enabled or disabled consumers.

8.1. Consumer details

By going on “View Details” more useful information about the consumer can be
accessed.

Merchant Console User Guide 72

Version 6.5 – February 2024
Here is an example of a detailed information displayed for one specific consumer:

If the cardholder’s details have not been tokenised the section “Saved Cards” does not
exist. In this view, the visible additional information could be the Billing address,
Payment transactions and WPF Payments. Here are the individual sections:

- Payment Transactions have the following columns: Actions, ID, Created at,
Merchant, Terminal, Type, Status, Error, Merchant Transaction ID, Unique ID,
Transaction ID, Card Holder, Card Number, Amount, Ref.

- WPF Payments have the following columns: ID, Date, Merchant, Terminal, MID,
Status, Customer, Amount.

- Saved Cards contain: Token ID, Token Type, Status, Created at, Expires at.
In case the cardholder details have been tokenised, the section “Saved Cards” appears
right under the section “Payment transactions”. To see how many card details have been
tokenised, users must click on the up arrow to expand the information.

Merchant Console User Guide 73

Version 6.5 – February 2024
 - Billing address

Please be aware that the Billing address can be updated using the Consumer API together
with the credit card number and other consumer information.

9. Virtual Terminal

The Virtual Terminal is used for processing mail order/telephone order (MOTO)
transactions. Those transactions are processed by the merchant on the behalf of the
customer. They are considered as riskier than normal eCommerce transactions, where the
customer places the transaction by themselves.
You must log in using your account to the gateway and navigate to the menu – “Virtual

Terminal” , located in the left main navigation.

Depending on your account configuration, your user account may have different options
for processing Virtual Terminal transactions.

Merchant Console User Guide 74

Version 6.5 – February 2024
Some of the transactions require the cardholder to participate in the process such as 3D
authentication at the issuer payment page.
Almost all the transactions made through a Virtual Terminal require the selection of a
processing terminal, it will contain a shortened name of the company, the descriptor, and
the currency:

If this terminal belongs to a merchant who supports FX rates, then a new field will appear
containing a dropdown list where a rate can be selected:

The amount field is also placed just below the terminal.

The amount must be filled in as per the input text box and the decimal point considered
depending on the currency exponent.
It is also possible for the merchants to ask for a lightweight access, so after logging in the
user will have access only to the “Virtual Terminal”:

By clicking on Pay by Link, the user will be able to easily generate a link for the payment
(Pay by Link will be available depending on your account configuration).

Merchant Console User Guide 75

Version 6.5 – February 2024
By clicking on MOTO, you will be performing a Sale transaction:

9.1. Authorize

The Authorization is an initial transaction type which requires Capture (settlement) for
such transaction to become financial for the end customer. Capture processing with
Virtual Terminal will be covered below.
To process an Authorization transaction with the Virtual Terminal please click on the
Virtual Terminal button and click on the Authorize link. Some basic details will be
needed to process an Authorize transaction.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 76

Version 6.5 – February 2024
 • Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, CVV/CVC2 number, Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Dynamic descriptor – If enabled in account configuration, the Dynamic
descriptor could be used.

After filling in all mandatory details (*) from the Virtual Terminal form you can click the
Process button and wait for a response.

• If the transaction is successful, a Payment Confirmation table will be shown. From

the Payment confirmation table, you should note/copy the value of the unique_id.
It will be used for capturing the transaction.
• If the transaction is declined, a table showing the error will appear.

To open the payment transaction, you have just made click on the button “Show Payment
Transaction”.

9.2. Authorize3D

Merchant Console User Guide 77

Version 6.5 – February 2024
The Authorize3D is an initial transaction type which requires Capture (settlement) for
such transaction to become financial for the end customer. Capture processing with
Virtual Terminal will be covered below. The Authorize3D transaction in addition to the
normal (CVV ON) authorisation will add 3D secure authentication at the issuer page.
To process an Authorization transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Authorize3D link. Some basic details will be
needed to process an Authorize3D.
In the Details section for Authorize3D, the following URL addresses for 3D must be
added to the form as well: notification_url, return_success_url and return_failure_url.

The rest of the details are filled in the respective sections:

• Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, Card Number, CVV/CVC2 number,
Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Dynamic descriptor – If enabled in account configuration, the Dynamic
descriptor could be used.

After filling in all mandatory details (*) from the Virtual Terminal form you can click the
Process button and wait for a response.

• If the transaction is successful, a Payment Confirmation table will be shown. From

the Payment confirmation table, you should note/copy the value of the unique_id.
It will be used for capturing the transaction.
• If the transaction is declined, a table showing the error will appear.

Merchant Console User Guide 78

Version 6.5 – February 2024
To open the payment transaction, you have just made click on the button “Show Payment
Transaction”.

9.3. Capture

To finalise and make the authorisation transaction a financial transaction, a Capture must
be performed.
To Capture an Authorize / Authorize3D transaction, please click on the Virtual Terminal
button and click on the Capture link.
From the menu Terminal a proper terminal must be selected. The terminal must be the
same as the Terminal where the authorisation has been processed.
In the field reference_id, please input the unique_id returned from the authorise response
within the field unique_id.

9.4. Sale

The Sale transaction is an initial transaction type and has a direct financial impact to the
end customer.
To process a Sale transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Sale link. Some basic details will be needed to process a
Sale.
The rest of the details are filled in the respective sections:

• Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, Card Number, CVV/CVC2 number,
Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 79

Version 6.5 – February 2024
 • Dynamic descriptor – If enabled in account configuration, the Dynamic
descriptor could be used.

After filling in all mandatory details (*) from the Virtual Terminal form, you can click
the Process button and wait for a response.

• If the transaction is successful, a Payment Confirmation table will be shown.

• If the transaction is declined, a table showing the error will appear.

To open the payment transaction, you have just made click on the button “Show Payment
Transaction”.

9.5. Sale3D

The Sale3D transaction is an initial transaction type and has a direct financial impact to
the end customer. The Sale3D transaction in additional to the normal (CVV ON) sale will
add 3D secure authentication at the issuer page.
To process a Sale3D transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Sale3D link. Some basic details will be needed to
process a Sale3D.
In the Details section for Sale3D, the following URL addresses for 3D must be added to
the form as well: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, Card Number, CVV/CVC2 number,
Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 80

Version 6.5 – February 2024
 • Dynamic descriptor – If enabled by account configuration the Dynamic
descriptor could be used.

After filling in all mandatory details (*) from the Virtual Terminal form, you can click
the Process button and wait for a response.

• If the transaction is successful, a Payment Confirmation table will be shown.

• If the transaction is declined, a table showing the error will appear.

To open the payment transaction, you have just made click on the button “Show Payment
Transaction”.

9.6. Init recurring sale

To process an Init recurring sale transaction, click the Virtual Terminal button and then
the Init recurring sale link. Some basic details will be needed to process an Init recurring
sale.
Init recurring sale is processed like the normal Sale transaction, but it provides the
possibility for recurring. Please refer to the Sale transaction section from the guide. Init
recurring sale is used for subsequent recurring transactions.
After a successful Init recurring sale transaction, using the unique_id parameter returned,
a RecurringSale transactions could be submitted. Or a new Managed Recurring Item can
be created for an automatic charge to the customer if the merchant is configured to
support this feature.

9.7. Init recurring sale3d

Please refer to the 7.6. Init recurring sale section. The additional is that a 3D
authentication is performed, and three URLs must be filled - notification_url,
return_success_url and return_failure_url.

Merchant Console User Guide 81

Version 6.5 – February 2024
9.8. Recurring sale

To process a RecurringSale transaction, click the Virtual Terminal button and then click
the RecurringSale link. Some basic details will be needed to process a Recurring sale.
RecurringSale transaction type via the Virtual Terminal requires a unique id from an Init
recurring sale which should be included in the reference_id field.

9.9. Account Verification

Account verification is a transaction that does not have a financial impact on the
customer.
To submit an Account verification transaction, click the Virtual Terminal button and then
click the Account verification link.
The following fields must be filled depending on the account configuration:

• Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, Card Number, CVV/CVC2 number,
Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.10. Credit

To submit Credit transaction, click the Virtual Terminal button and then then click the
Credit link.

Merchant Console User Guide 82

Version 6.5 – February 2024
Then a processing terminal must be selected. The terminal contains the shortened text of
the company, the descriptor, and the currency.
The amount must be filled as per the input text box and the decimal point considered
depending on the currency exponent.
The Credit transaction type via the Virtual Terminal requires to be referred by a Unique
ID from a Sale, sale3D or capture which should be included in the reference_id field.
As Source of funds, the following options can be selected (only applicable for
transactions with the Visa card brand):

• Credit – Visa credit

• Debit – Visa debit
• Prepaid – Visa prepaid
• Cash
• other_debit_account - Debit/deposit access accounts other than those linked to a
Visa Card (includes checking/savings accounts and proprietary debit/ATM cards).
• other_credit_account - Credit accounts other than those linked to a Visa Card
(includes Credit Cards and proprietary credit lines).

9.11. Payout

Merchant Console User Guide 83

Version 6.5 – February 2024
To process a Payout transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Payout link. Some basic details will be needed to
process a Payout.
The rest of the details are filled in the respective sections:

• Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Sender Details – Section where additional details about the sender of the payout
are provided.
• Money Transfer Type: Special attribute for Payouts – needs also to be
enabled on Merchant Level. Genesis supports several types of transfers,
this field can take the following values: Account to Account, Person to
person, Wallet Transfer, Business to business Supplier Payments, Loyalty
Payments, Funds Disbursement, Merchant Settlement and Prepaid Card
Load.
• Source of funds - The following options can be selected (only applicable
for transactions with the Visa card brand):
- Credit – Visa credit
- Debit – Visa debit
- Prepaid – Visa prepaid
- Cash
- other_debit_account - Debit/deposit access accounts other than those linked
to a Visa Card (includes cheking/savings accounts and proprietary
debit/ATM cards). This is the default if no other value is selected.

Merchant Console User Guide 84

Version 6.5 – February 2024
 - other_credit_account - Credit accounts other than those linked to a Visa
Card (includes Credit Cards and proprietary credit lines).

9.12. eZeeCard Payout

eZeeCard Payout is a sync-based payout method. It is merchant initiated and can only
reference specific transaction types: Capture, Sale, Sale3D, InitRecurringSale,
InitRecurringSale3D and RecurringSale
To process an eZeeCard Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the eZeeCard Payout link. Some basic details will
be needed to process an eZeecard Payout. Reference ID – Unique ID returned by THE
corresponding transaction.

• eZeeCard Payout has amount limits of a minimum of 10 EUR and a maximum of

800 EUR per transaction or its equivalent in other currencies.

9.13. Incremental Authorize

Incremental authorisations are used in pre-authorisation workflow to:

- extend the pre-authorisation amount

- extend the pre-authorisation timeframe

Incremental authorisations are non-3DS because they only refer to the Pre-authorisation
transaction. They cannot be voided/refunded etc, and can only modify/extend the related
pre-authorisation.
An incremental authorisation transaction can be submitted in case:

Merchant Console User Guide 85

Version 6.5 – February 2024
 - Pre-authorisation is approved and pre-authorisation timeframe has not expired.
- Pre-authorisation has not been captured.

To process an Incremental Authorize transaction with the Virtual Terminal, please click
on the Virtual Terminal button and click on the Incremental Authorize link. Some basic
details will be needed to process an Incremental Authorize.
The rest of the details are filled in the respective sections:

• Reference ID - Unique ID of the corresponding pre-authorisation transaction.

9.14. Partial Reversal

Partial reversal transactions are used in pre-authorisation workflow to release a part of

the total authorised amount regardless of whether a partial capture has already been
submitted or not. A transaction of this type should refer to the pre-authorisation directly.
Merchants are not obliged to submit partial reversal for the amount left before the capture
transaction. In other terms, the partial capture does not require a partial reversal.
The partial reversals can be submitted no later than 24 hours after the pre-authorisation is
about to expire.
To process a Partial Reversal transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Partial Reversal link. Some basic details will be
needed to process a Partial Reversal.
The rest of the details are filled in the respective sections:

• Reference ID - Unique ID of the corresponding pre-authorisation transaction.

9.15. CashU

To process a CashU transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the CashU link. Some basic details will be needed to
process a CashU transaction.

Merchant Console User Guide 86

Version 6.5 – February 2024
For the CashU method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.16. Paysafecard

To process a Paysafecard transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Paysafecard link. Some basic details will be
needed to process a Paysafecard transaction.
For the Paysafecard method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.17. eZeeWallet

To process an eZeeWallet transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the eZeeWallet link. Some basic details will be
needed to process an eZeeWallet transaction.

Merchant Console User Guide 87

Version 6.5 – February 2024
For the eZeeWallet method the following fields / addresses must be filled
return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those are the fields: Consumer email and
Consumer password.

9.18. Sofort

To process a Sofort transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Sofort link. Some basic details will be needed to process
a Sofort transaction.
For the Sofort method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Sofort specific fields: Customer Bank ID and Bank Account Number must be
filled as well.

9.19. PPRO

To process a PPRO transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the PPRO link. Some basic details will be needed to process
a PPRO transaction. A PPRO sub-method must be selected as well.

Merchant Console User Guide 88

Version 6.5 – February 2024
For the PPRO method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• PPRO specific fields: BIC, IBAN, Account Phone, Bank Code, Account Number.

9.20. Neteller

To process a Neteller transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Neteller link. Some basic details will be needed to
process a Neteller transaction.
For the Neteller method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this

Merchant Console User Guide 89

Version 6.5 – February 2024
 section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Neteller specific fields: Customer Email/Account and Account Password.

9.21. ABN iDeal

To process an ABN iDeal transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the ABN iDeal link. Some basic details will be
needed to process an ABN iDeal transaction.
For the ABN iDeal method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• ABN iDeal specific fields: Bank.

9.22. Webmoney

To process a Webmoney transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Webmoney link. Some basic details will be
needed to process a Webmoney transaction.
For the Webmoney method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 90

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Webmoney specific fields: Customer Account ID.

9.23. POLi

To process a POLi transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the POLi link. Some basic details will be needed to process
a POLi transaction.
For the POLi method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.24. Paybyvoucher sale

To process a Paybyvoucher sale transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Paybyvoucher sale link. Some basic details will
be needed to process a Paybyvoucher transaction.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 91

Version 6.5 – February 2024
 • Credit Card Information – This is the section where the sensitive customer
information is filled: Card Number, Card Number, CVV/CVC2 number,
Expiration date.
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Dynamic descriptor – If enabled in account configuration, the Dynamic
descriptor could be used.

9.25. SDD Sale

To process an SDD Sale transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the SDD Sale link. Some basic details will be needed to
process an SDD transaction.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: First name, Last name.
• SDD Sale specific fields: IBAN, BIC.

9.26. SDD Init Recurring Sale

To process an SDD Init Recurring Sale transaction with the Virtual Terminal, please
click on the Virtual Terminal button and click on the SDD Init Recurring Sale link. Some
basic details will be needed to process a SDD Init Recurring Sale transaction.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 92

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: First name, Last name.
• SDD Sale specific fields: IBAN, BIC.

9.27. SDD Recurring Sale

To process an SDD Recurring Sale transaction with the Virtual Terminal, please click on
the Virtual Terminal button and click on the SDD Recurring Sale link. Some basic details
will be needed to process an SDD Recurring Sale transaction.
The SDD Recurring Sale transaction type via the Virtual Terminal requires to be referred
by a Unique ID from an SDD Init Recurring Sale which should be included in the
Reference ID field.

9.28. SDD Refund

To process an SDD Refund transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the SDD Refund link. Some basic details will be
needed to process an SDD Refund transaction.
The SDD Refund transaction type via the Virtual Terminal requires to be referred by a
Unique ID from an approved SDD deposit type of transaction which should be included
in the Reference ID field.

9.29. Przelewy24

To process a Przelewy24 transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Przelewy24 link. Some basic details will be
needed to process a Przelewy24 transaction.

Merchant Console User Guide 93

Version 6.5 – February 2024
For the Przelewy24 method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.30. SCT Payout

To process an SCT Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the SCT Payout link. Some basic details will be
needed to process an SCT Payout transaction.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: First name, Last name.
• STC Payout specific fields: IBAN, BIC.

9.31. Trustly Sale

To process a Trustly Sale transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Trustly Sale link. Some basic details will be
needed to process a Trustly Sale transaction.

Merchant Console User Guide 94

Version 6.5 – February 2024
In the Details section for Trustly Sale, the following URL addresses for 3D must be
added to the form as well: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective section:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to mandatory,
depending on the account configuration. The possible fields in this section are as
follows: Email, Phone, First name, Last name, Primary Address, Secondary Address,
Zip Code, City, Country, State.

9.32. Trustly Withdrawal

To process a Trustly Withdrawal transaction with the Virtual Terminal, please click on
the Virtual Terminal button and click on the Trustly Withdrawal link. Some basic details
will be needed to process a Trustly Withdrawal transaction.
In the Details section for Trustly Withdrawal the following URL addresses for 3D must
be added to the form as well: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective section:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to mandatory,
depending on the account configuration. The possible fields in this section are as
follows: Email, Phone, First name, Last name, Primary Address, Secondary Address,
Zip Code, City, Country, State.
• Trustly specific fields: Birth Date.

9.33. PayPal Express Checkout

Merchant Console User Guide 95

Version 6.5 – February 2024
To process a PayPal transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the PayPal Express Checkout link. Some basic details will
be needed to process a PayPal Express Checkout transaction.
For the PayPal Express Checkout method and due to the asynchronous design, the
following fields / addresses must be filled: notification_url, return_success_url,
return_failure_url and Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, First name, Last name, Primary address, Zip code,
City, Country.

9.34. iDebit Payin

To process an iDebit Payin transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the iDebit Payin link. Some basic details will be
needed to process an iDebit Payin transaction.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• iDebit Payin specific fields: Customer Account number or ID.

9.35. iDebit Payout

Merchant Console User Guide 96

Version 6.5 – February 2024
To process an iDebit Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the iDebit Payout link. Some basic details will be
needed to process an iDebit Payout transaction.
The rest of the details are filled in the respective sections:

• iDebit Payout specific fields: Approved InstaDebit Payin transaction Unique ID.

9.36. InstaDebit Payin

To process an InstaDebit Payin transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the InstaDebit Payin link. Some basic details will be
needed to process an InstaDebit Payin transaction.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• InstaDebit Payin specific fields: Customer Account number or ID.

9.37. InstaDebit Payout

To process an InstaDebit Payout transaction with the Virtual Terminal please click on
Virtual Terminal button and click on the InstaDebit Payout link. Some basic details will
be needed to process an InstaDebit Payout transaction.
The rest of the details are filled in the respective sections:

• InstaDebit Payout specific fields: Approved InstaDebit Payin transaction Unique

ID.

Merchant Console User Guide 97

Version 6.5 – February 2024
9.38. Earthport

To process an Earthport transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Earthport link. Some basic details will be needed to
process an Earthport transaction.
For the Earthport method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.39. WeChat Pay

To process a WeChat Pay transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the WeChat Pay link. Some basic details will be
needed to process a WeChat Pay transaction.
For the WeChat Pay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• WeChat Pay specific fields: Product code; Product number; Product description.

Merchant Console User Guide 98

Version 6.5 – February 2024
9.40. Alipay

To process an Alipay transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Alipay link. Some basic details will be needed to
process an Alipay transaction.
For the Alipay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.41. Online Banking

To process an Online Banking transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Online Banking link. Some basic details will be
needed to process an Online Banking transaction.
For the Online Banking method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 99

Version 6.5 – February 2024
9.42. Bank Payout

To process a Bank Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Bank Payout link. Some basic details will be
needed to process a Bank Payout transaction.
For the Bank Payout method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url, return_failure_url and
Select payment type.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Bank Payout specific fields: Payment type (customers will need to select a
payout subtype), Bank Code; Bank Name; Bank Branch; Bank Account Name;
Bank Account Number.

9.43. RPN Payout

To process an RPN Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the RPN Payout link. Some basic details will be
needed to process an RPN Payout transaction.
RPN Payout specific fields: Bank Name, Sub Branch, Bank Account Name, Bank Card
Number, Province, Area.

9.44. Intersolve

Merchant Console User Guide 100

Version 6.5 – February 2024
To process an Intersolve transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Intersolve link. Some basic details will be needed to
process an Intersolve transaction.
Intersolve specific fields: Card number and Verification code.

9.45. Fashioncheque

To process a Fashioncheque transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Fashioncheque link. Some basic details will be
needed to process a Fashioncheque transaction.
Fashioncheque specific fields: Card number and Verification code.

9.46. The Container Store (TCS)

To process a TCS transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the TCS link. Some basic details will be needed to process
a TCS transaction.
TCS specific fields: Card number and Verification code.

9.47. Paycommerce

To process a Paycommerce transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Paycommerce link.
Select Merchant:

Click on Batch File to open PopUp to select and upload CSV file (in strictly defined
format, check the Paycommerce section in API documentation).

Merchant Console User Guide 101

Version 6.5 – February 2024
Genesis validates the provided data and if it is OK, initial batch file is built matching the
required Paycommerce format and PaycommerceTransactions in status
pending_asynchronous are created.
A Member of Treasury reviews the uploaded batches and approves them if the Merchant
has enough funds for the requested payouts.

9.48. Neosurf

To process a Neosurf transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Neosurf link. Some basic details will be needed to
process a Neosurf transaction.
For the Neosurf method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Neosurf specific fields: Voucher Number.

9.49. TransferTo Payout

Merchant Console User Guide 102

Version 6.5 – February 2024
TransferTo Payout is an APM which provides three different payment services:
BankAccount, MobileWallet and CashPickup. A merchant sends money to a consumer.
The money is delivered through a Payer institution which supports one of the three
services and has specific requirements on the transaction’s amount and required fields.
The process is asynchronous and once TransferTo process the transaction, a notification
is received, and the status is updated.
To process a TransferTo Payout transaction with the Virtual Terminal please click on
Virtual Terminal button and click on the TransferTo Payout link. Some basic details will
be needed to process a TransferTo Payout transaction.
For the TransferTo Payout method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Money Transfer Type – Business to Client or Business to Business
• Payer ID - ID of the Payer used to deliver the money through one of the three
services.

9.50. UPI

To process a UPI transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the UPI link. Some basic details will be needed to process a
UPI transaction.

Merchant Console User Guide 103

Version 6.5 – February 2024
For the UPI method and due to the asynchronous design, the following fields / addresses
must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• UPI specific fields: Virtual payment address.

9.51. Invoice

To process an Invoice transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Invoice link. Some basic details will be needed to
process an Invoice transaction.
For the Invoice method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, Gender, First name, Last name, Primary
Address, Secondary Address, Zip Code, City, Country, State.
• Items – must be provided at least one item – up to five with several required
fields, such as: Item type, Name, Quantity, Unit price and Total amount.

Merchant Console User Guide 104

Version 6.5 – February 2024
9.52. Invoice Capture

To process an Invoice Capture transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Invoice Capture link. Some basic details will be
needed to process an Invoice Capture transaction.

Reference ID must be filled as per the input text box.

• Items – must be provided at least one item – up to five with several required
fields, such as: Item type, Name, Quantity, Unit price and Total amount.

Merchant Console User Guide 105

Version 6.5 – February 2024
9.53. Invoice Refund

Invoice Refund is a transaction which transfers the money back to the end customer in
case if the customer is not satisfied by the service or similar case. Refund can be only
initiated on transactions with a financial impact such as Invoice Capture.
To perform an Invoice Refund transaction, click on the Virtual Terminal and click
Invoice Refund.
To process the Invoice Refund, please use the unique_id from a financial transaction and
input it in the field reference_id.
If the Refund is successful, a message showing that the refund was successful will be
shown.

Merchant Console User Guide 106

Version 6.5 – February 2024
9.54. BitPay

BitPay is a cryptocurrency payments provider supporting blockchain payments with

Bitcoin (BTC) and BitcoinCash (BCH). BitPay Sale is an asynchronous transaction type.
When this payment method is selected at checkout, the customer will be redirected to the
BitPay system window including all the data for the payment: Bitcoin/BitcoinCash
account, amount to be paid in cryptocurrency and the Fiat equivalent.
If the customer possesses a BitPay wallet or another BitPay-compatible crypto wallet, the
payment can be done from that window with one click, otherwise, a QR CODE
containing all the payment data can be scanned and used in any crypto wallet.
The customer has 15 minutes to fulfil the generated invoice. If that timeframe is not met,
the invoice will expire, and the Merchant will be notified.
If the invoice is fulfilled in the timeframe, it needs to obtain six blockchain confirmations
(~1 hour) before it’s safe for the payment to be considered as completed.
At that point, the Merchant will be notified about the approved payment.
After the 6th confirmation, when the transaction is completed, the Merchant can process
a refund if necessary.
Each transaction has amount limits of a minimum 1 USD and a maximum of 950 000
USD or its equivalent in EUR.
To process a BitPay transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the BitPay link. Some basic details will be needed to
process a BitPay transaction.
For the BitPay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from option to mandatory,
depending on the account configuration. The possible fields in this section are as
follows: Email, Phone, First name, Last name, Primary Address, Secondary
Address, Zip Code, City, Country, State.

Merchant Console User Guide 107

Version 6.5 – February 2024
9.55. BitPay Payout

BitPay Payout is a cryptocurrency payout method where merchants are requesting

payouts in FIAT currency and the funds are transferred in Bitcoin equivalent to a crypto
wallet address. BitPay Payout is an asynchronous transaction type supported through the
Processing API, Virtual Terminal, and Web Payment Form.
The payout requests are processed once a day at 11:00 GMT and the settlement usually
takes 24 hours.
For amounts greater than 3000 USD or equivalent in other currencies, additional KYC
authentication might be required by BitPay.
Each transaction has amount limits of a minimum 1 USD and a maximum of 950 000
USD or its equivalent in EUR.
To process a BitPay Payout transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the BitPay Payout link. Some basic details will be
needed to process a BitPay Payout transaction.
For the BitPay Payout method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Crypto Transaction Details:

- Crypto Address - Valid crypto address where the funds will be received
- Crypto Wallet Provider - If crypto wallet provider is not included in the
dropdown menu, you must choose ‘other’
• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 108

Version 6.5 – February 2024
9.56. BitPay Refund

BitPay Refund is a custom refund method which handles the asynchronous BitPay refund
workflow. BitPay refunds can only be done on former transactions. Therefore, the
Reference ID for the corresponding BitPay Sale transaction is mandatory. BitPay Refund
is an asynchronous transaction type.
When a BitPay Refund is requested, BitPay will send an email to the consumer with a
request to provide the refund crypto address. This request will be valid for three days and
will expire afterwards. When the crypto address is provided, the refund will be processed
(processing usually takes 24 hours).
A notification will be sent to the Merchant when the Bitpay refund is completed. Only
full refunds are supported at the moment.
BitPay Refunds can be voided only during the 24-hour processing period.
To process a BitPay Refund transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the BitPay Refund link. Some basic details will be
needed to process a BitPay Refund transaction.
For the BitPay Refund method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.57. African Mobile Sale

African Mobile Sale, otherwise known as Charge, is an APM used to process Mobile
network operator payments. It is an asynchronous payment method and will be approved
once African Mobile processes the payment with the Mobile network operator.

Merchant Console User Guide 109

Version 6.5 – February 2024
To process an African Mobile Sale transaction with the Virtual Terminal, please click on
the Virtual Terminal button and click on the African Mobile Sale link. Some basic details
will be needed to process an African Mobile Sale transaction.
For the African Mobile Sale method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Operator – Name of the Mobile network operator (MNO) which should process
the transaction - VODACOM, SAFARICOM, AIRTEL, MTN.
• Target - Number of the Paybill for which the transaction is intended.

9.58. African Mobile Payout

African Mobile Payout, otherwise known as Disbursement, is an APM used to process

Mobile network operator payments. It is an asynchronous payment method and will be
approved once African Mobile processes the payment with the Mobile network operator.
To process an African Mobile Payout transaction with the Virtual Terminal, please click
on the Virtual Terminal button and click on the African Mobile Payout link. Some basic
details will be needed to process an African Mobile Payout transaction.
For the African Mobile Payout method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 110

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Operator – Name of the Mobile network operator (MNO) which should process
the transaction - VODACOM, SAFARICOM, AIRTEL, MTN.
• Target - Number of the Paybill for which the transaction is intended.

9.59. Astropay Direct

To process an Astropay Direct transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Astropay Direct link. Some basic details will be
needed to process an Astropay Direct transaction.
For the Astropay Direct method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Astropay Direct specific fields: Consumer Reference.

Merchant Console User Guide 111

Version 6.5 – February 2024
9.60. Bancontact

To process a Bancontact transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Bancontact link. Some basic details will be needed to
process a Bancontact transaction.
For the Bancontact method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.61. QIWI

To process a QIWI transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the QIWI link. Some basic details will be needed to process
a QIWI transaction.
For the QIWI method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• QIWI specific fields: Site ID.

Merchant Console User Guide 112

Version 6.5 – February 2024
9.62. MyBank

To process a MyBank transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the MyBank link. Some basic details will be needed to
process a MyBank transaction.
For the MyBank method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.63. Giropay

To process a Giropay transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Giropay link. Some basic details will be needed to
process a Giropay transaction.
For the Giropay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Giropay specific fields: BIC.

Merchant Console User Guide 113

Version 6.5 – February 2024
9.64. Zimpler

To process a Zimpler transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Zimpler link. Some basic details will be needed to
process a Zimpler transaction.
For the Zimpler method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.65. Safetypay

To process a Safetypay transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Safetypay link. Some basic details will be needed to
process a Safetypay transaction.
For the Safetypay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 114

Version 6.5 – February 2024
9.66. PayU

To process a PayU transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the PayU link. Some basic details will be needed to process
a PayU transaction.
For the PayU method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.67. Instant Transfer

To process an Instant Transfer transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Instant Transfer link. Some basic details will be
needed to process an Instant Transfer transaction.
For the Instant Transfer method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Instant Transfer specific fields: IBAN and BIC.

Merchant Console User Guide 115

Version 6.5 – February 2024
9.68. Multibanco

To process a Multibanco transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Multibanco link. Some basic details will be
needed to process a Multibanco transaction.
For the Multibanco method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.69. iDEAL

To process an iDEAL transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the iDEAL link. Some basic details will be needed to
process an iDEAL transaction.
For the iDEAL method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.70. EPS

Merchant Console User Guide 116

Version 6.5 – February 2024
To process an EPS transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the EPS link. Some basic details will be needed to process
an EPS transaction.
For the EPS method and due to the asynchronous design, the following fields / addresses
must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

9.71. Pago Facil

To process a Pago Facil transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Pago Facil link. Some basic details will be needed to
process a Pago Facil transaction.
For the Pago Facil method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Pago Facil specific fields: Birth Date, Consumer Reference, and National ID.

9.72. PSE

Merchant Console User Guide 117

Version 6.5 – February 2024
To process a PSE transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the PSE link. Some basic details will be needed to process a
PSE transaction.
For the PSE method and due to the asynchronous design, the following fields / addresses
must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• PSE specific fields: Birth Date, Consumer Reference, and National ID.

9.73. Rapipago

To process a Rapipago transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Rapipago link. Some basic details will be needed to
process a Rapipago transaction.
For the Rapipago method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Rapipago specific fields: Birth Date, Consumer Reference, and National ID.

9.74. WebPay

Merchant Console User Guide 118

Version 6.5 – February 2024
To process a WebPay transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Webpay link. Some basic details will be needed to
process a Webpay transaction.
For the Webpay method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as following: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• WebPay specific fields: Birth Date, Consumer Reference, and National ID.

9.75. Carulla

To process a Carulla transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Carulla link. Some basic details will be needed to
process a Carulla transaction.
For the Carulla method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Carulla specific fields: Birth Date, Consumer Reference, and National ID.

9.76. Davivienda

Merchant Console User Guide 119

Version 6.5 – February 2024
To process a Davivienda transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Davivienda link. Some basic details will be
needed to process a Davivienda transaction.
For the Davivienda method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Davivienda specific fields: Birth Date, Consumer Reference, and National ID.

9.77. Surtimax

To process a Surtimax transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Surtimax link. Some basic details will be needed to
process a Surtimax transaction.
For the Surtimax method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Surtimax specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 120

Version 6.5 – February 2024
9.78. OXXO

To process an OXXO transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the OXXO link. Some basic details will be needed to
process an OXXO transaction.
For the OXXO method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• OXXO specific fields: Birth Date, Consumer Reference, and National ID.

9.79. Efecty

To process an Efecty transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Efecty link. Some basic details will be needed to
process an Efecty transaction.
For the Efecty method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Efecty specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 121

Version 6.5 – February 2024
9.80. Argencard

To process an Argencard transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Argencard link. Some basic details will be
needed to process an Argencard transaction.
For the Argencard method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Argencard specific fields: Birth Date, Consumer Reference, and National ID.

9.81. Naranja

To process a Naranja transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Naranja link. Some basic details will be needed to
process a Naranja transaction.
For the Naranja method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Naranja specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 122

Version 6.5 – February 2024
9.82. Nativa

To process a Nativa transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Nativa link. Some basic details will be needed to
process a Nativa transaction.
For the Nativa method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Nativa specific fields: Birth Date, Consumer Reference, and National ID.

9.83. Cabal

To process a Cabal transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Cabal link. Some basic details will be needed to process
a Cabal transaction.
For the Cabal method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Cabal specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 123

Version 6.5 – February 2024
9.84. Cencosud

To process a Cencosud transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Cencosud link. Some basic details will be needed to
process a Cencosud transaction.
For the Cencosud method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Cencosud specific fields: Birth Date, Consumer Reference, and National ID.

9.85. Hipercard

To process a Hipercard transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Hipercard link. Some basic details will be needed to
process a Hipercard transaction.
For the Hipercard method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Hipercard specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 124

Version 6.5 – February 2024
9.86. Elo

To process an Elo transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Elo link. Some basic details will be needed to process
an Elo transaction.
For the Elo method and due to the asynchronous design, the following fields / addresses
must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Elo specific fields: Birth Date, Consumer Reference, and National ID.

9.87. Aura

To process an Aura transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Aura link. Some basic details will be needed to process
an Aura transaction.
For the Aura method and due to the asynchronous design, the following fields / addresses
must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Aura specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 125

Version 6.5 – February 2024
9.88. Astropay Card

To process an Astropay Card transaction with the Virtual, Terminal please click on the
Virtual Terminal button and click on the Astropay Card link. Some basic details will be
needed to process an Astropay Card transaction.
For the Astropay Card method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Astropay Card specific fields: Consumer Reference.

9.89. Banco Itaú

To process a Banco Itaú transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Banco Itaú link. Some basic details will be needed to
process a Banco Itaú transaction.
For the Banco Itaú method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Banco Itaú specific fields: Birth Date, Consumer Reference, and National ID.

Merchant Console User Guide 126

Version 6.5 – February 2024
9.90. Bradesco

To process a Bradesco transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Bradesco link. Some basic details will be needed to
process a Bradesco transaction.
For the Bradesco method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Bradesco specific fields: Birth Date, Consumer Reference, and National ID.

9.91. Tarjeta Shopping

To process a Tarjeta Shopping transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Tarjeta Shopping link. Some basic details will
be needed to process a Tarjeta Shopping transaction.
For the Tarjeta Shopping method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 127

Version 6.5 – February 2024
 • Tarjeta Shopping specific fields: Birth Date, Consumer Reference, and National
ID.

9.92. BBVA Bancomer

To process a BBVA Bancomer transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the BBVA Bancomer link. Some basic details will
be needed to process a BBVA Bancomer transaction.
For the BBVA Bancomer method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• BBVA Bancomer specific fields: Birth Date, Consumer Reference, and National
ID.

9.93. Boleto Bancario

To process a Boleto Bancario transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Boleto Bancario link. Some basic details will be
needed to process a Boleto Bancario transaction.
For the Boleto Bancario method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 128

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Boleto Bancario specific fields: Birth Date, Consumer Reference, and National
ID.

9.94. Redpagos

To process a Redpagos transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Redpagos link. Some basic details will be needed to
process a Redpagos transaction.
For the Redpagos method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Redpagos specific fields: Birth Date, Consumer Reference, and National ID.

9.95. Santander

To process a Santander transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Santander link. Some basic details will be needed to
process a Santander transaction.
For the Santander method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

Merchant Console User Guide 129

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Santander specific fields: Birth Date, Consumer Reference, and National ID.

9.96. Santander Cash

To process a Santander Cash transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Santander Cash link. Some basic details will be
needed to process a Santander Cash transaction.
For the Santander Cash method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Santander Cash specific fields: Birth Date, Consumer Reference, and National
ID.

9.97. Baloto

To process a Baloto transaction with the Virtual Terminal, please click on the Virtual
Terminal button and click on the Baloto link. Some basic details will be needed to
process a Baloto transaction.
For the Baloto method and due to the asynchronous design, the following fields /
addresses must be filled: notification_url, return_success_url and return_failure_url.

Merchant Console User Guide 130

Version 6.5 – February 2024
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Baloto specific fields: Birth Date, Consumer Reference, and National ID.

9.98. Empresa de Energia

To process an Empresa de Energia transaction with the Virtual Terminal, please click on
the Virtual Terminal button and click on the Empresa de Energia link. Some basic details
will be needed to process an Empresa de Energia transaction.
For the Empresa de Energia method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Empresa de Energia specific fields: Birth Date, Consumer Reference, and
National ID.

9.99. Banco de Occidente

Merchant Console User Guide 131

Version 6.5 – February 2024
To process a Banco de Occidente transaction with the Virtual Terminal, please click on
the Virtual Terminal button and click on the Banco de Occidente link. Some basic details
will be needed to process a Banco de Occidente transaction.
For the Banco de Occidente method and due to the asynchronous design, the following
fields / addresses must be filled: notification_url, return_success_url and
return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Banco de Occidente specific fields: Birth Date, Consumer Reference, and
National ID.

9.100. Banco do Brasil

To process a Banco do Brasil transaction with the Virtual Terminal, please click on the
Virtual Terminal button and click on the Banco do Brasil link. Some basic details will be
needed to process a Banco do Brasil transaction.
For the Banco do Brasil method and due to the asynchronous design, the following fields
/ addresses must be filled: notification_url, return_success_url and return_failure_url.
The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 132

Version 6.5 – February 2024
 • Banco do Brasil specific fields: Birth Date, Consumer Reference, and National
ID.

9.101. Refund

Refund is a transaction which transfers the money back to the end customer in case the
customer is not satisfied by the service or similar case. Refund can be only initiated on
transactions with a financial impact such as Sale, Capture, Sale3D.
To perform a Refund transaction, click on the Virtual Terminal and click on Refund link.
To process the Refund, please use the unique_id from a financial transaction and input it
in the field reference_id.
If the Refund is successful a message showing that the refund was successful will be
shown.

9.102. Void

Void can be used for cancelling the transactions from the following types: authorize,
capture, sale, refund, recurring sale, init recurring sale within the current day.
To Void a transaction via the Virtual Terminal, please click on the Virtual Terminal
button and then click the Void link.
To Void a transaction, please use the unique_id from the above listed transaction types
and input it in the field reference_id.
If the Void is successful a message showing that the void was successful will be shown.

9.103. Apple Pay

Apple Pay is a payment method presented by Apple. It is an alternative way of doing

usual card payments via a new encrypted method. To process an Apple Pay transaction
via Virtual Terminal, you just need to navigate to the Virtual Terminal section and then

Merchant Console User Guide 133

Version 6.5 – February 2024
click on Apple Pay. The merchant needs to select an appropriate terminal that supports
ApplePay, set the transaction amount, and then select the desired payment type
(Authorize or Recurring). Apple Pay sends the encrypted cardholder and payment
information to the Merchant and then the token needs to be entered in the Payment token
field. The rest of the information is customer specific – Customer Information (Email and
Phone) and Billing Address (First Name, Last Name, Primary Address, Secondary
Address, Zip code, City, Country and State).

9.104. Pay By Link

Pay By Link is a payment method which provides merchants the possibility to send a
payment link to a customer via email or SMS (configurable). The option is available
through Virtual Terminal, where the merchant can generate a Pay By Link payment (if
the feature is enabled).

- Generating Pay By Link

The first step would be to select a Terminal through which the payment would be
processed. The next mandatory fields are the amount that the customer will be charged,
the transaction ID and the corresponding response URLs. The required or optional
customer details to be entered in the form are chosen by the admin on merchant
configuration level.

Merchant Console User Guide 134

Version 6.5 – February 2024
Then the merchant will need to choose the channel to send the link to the customer.
Three options are available: Only generate link, Email and SMS. Depending on the
merchant’s choice, the email field or the phone field will become mandatory:

Merchant Console User Guide 135

Version 6.5 – February 2024
Alternatively, the merchant can select the “Only generate link” option. With this option,
the payment link will not be sent to the customer, and it will be provided only to the
merchant. Afterwards, the merchant can send the link to the customer by themselves.
If the customer was created previously, then the merchant can choose their email from
the dropdown list. If not, the merchant can click on “New Customer Email” and add the
address of the new customer which will be available from now on for future purchases.

At the bottom of the page is where choosing which transaction type will be used, whether
the customer will have the option to pay later, or to receive payment reminders to
complete the purchase.

Merchant Console User Guide 136

Version 6.5 – February 2024
- Workflow
A customised email template can be used for sending a payment link or configuration of
a preferred method – email or SMS. When all the required fields are filled and the
mandatory initial payload is provided, a payment request to the Web Payment Form
(WPF) is started. If the result of the request is successful, the response would include a
redirect URL, which would be sent either via email or SMS to the customer – the channel
and the method (email or phone number) should be provided by the merchant when
initiating the Pay By Link payment.

The customer can complete the payment by following the link that he has been provided
with. The URL redirects to the merchant’s WPF where the redirection workflows are the
same as the ones provided in the WPF section. For checking the status of any Pay By
Link initiated payment, the WPF reconcile API could be used.

- Combination with “Pay Later” feature

The Pay By Link triggered payments are combined with the ‘Pay Later’ functionality
(available also for the WPF API). The Pay By Link form provides the ability to choose
whether the customer would have the option enabled/disabled to delay the payment and
complete it later. It also gives the ability of enqueuing reminders based on pre-configured
values. Each of the reminders that are sent to the end-user include the URL for payment
completion as well.
“Pay Later Settings” can be accessed under Configuration-Merchants – in the top
right corner of the page

Merchant Console User Guide 137

Version 6.5 – February 2024
For details on making changes on the “Reminders” options, navigate to Merchant
Configuration section.
For configuration options or any other additional questions, you can always contact Tech
Support at [email protected],

9.105. Google Pay

Google Pay is an online payment system developed by Google. To process a Google Pay
transaction via Virtual Terminal, you just need to navigate to the Virtual Terminal section
and then click on Google Pay. The merchant needs to select an appropriate terminal that
supports Google Pay, set the transaction amount, and then select the desired payment
type (Authorize, Recurring or Sale).
Google Pay requests a token to represent the card a user is trying to add from the bank
which issued that card. Once the token is issued, this card is now “tokenised”. Google
Pay sends the encrypted cardholder and payment information to the Merchant and then
the token needs to be entered in the Payment token field.
The rest of the information is customer specific - Customer Information (Email and
Phone) and Billing Address (First Name, Last Name, Primary Address, Secondary
Address, Zip code, City, Country, and State).

9.106. Russian Mobile Sale

Russian Mobile Sale is an APM used to process Mobile network operator payments.
All that is required from customers is to enter their mobile number in an online shop or
application and confirm payment by SMS.
To process a Russian Mobile Sale transaction via Virtual Terminal, you just need to
navigate to the Virtual Terminal section and then click on Russian Mobile Sale.

The rest of the details are filled in the respective sections:

Merchant Console User Guide 138

Version 6.5 – February 2024
 • Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Operator – Name of the Mobile network operator which should process the
transaction - Megafon, Beeline, MTS, Tele2.
• Target - Number of the Paybill for which the transaction is intended.

9.107. Russian Mobile Payout

Russian Mobile Payout is an APM used to process Mobile network operator payments.
All that is required from customers is to enter their mobile number in an online shop or
application and confirm payment by SMS.
To process a Russian Mobile Payout transaction via Virtual Terminal, you just need to
navigate to the Virtual Terminal section and then click on Russian Mobile Payout.

The rest of the details are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• Operator – Name of the Mobile network operator which should process the
transaction - Megafon, Beeline, MTS, Tele2.
• Target - Number of the Paybill for which the transaction is intended.

9.108. Pix

Pix is the brand created by the Central Bank of Brazil (BACEN). It is a new way of
receiving/sending money. It allows payments to be made instantly 24 hours a day, every

Merchant Console User Guide 139

Version 6.5 – February 2024
day of the year, including holidays. To process a Pix transaction via Virtual Terminal,
you just need to navigate to the Virtual Terminal section and then click on Pix. The
merchant needs to select an appropriate terminal that supports Pix, set the transaction
amount, and populate the mandatory fields.

The mandatory fields are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.
• PIX specific fields – Consumer Reference (Consumer reference is a unique
consumer identifier) and Document ID (The document ID of the consumer).

9.109. eWallet

Payments to our Indian partner FSS are now possible via eWallet. It enables you to make
an eWallet transaction using one of the following wallets: Freecharge; Amazon Pay;
Phonepe. To process an eWallet transaction via Virtual Terminal, you just need to
navigate to the Virtual Terminal section and then click on eWallet. The merchant needs
to select an appropriate terminal that supports eWallet, set the transaction amount, and
populate the mandatory fields.
The mandatory fields are filled in the respective sections:

• Customer information and Billing Address – These are the sections where the
specific customer information is filled. Those may vary from optional to
mandatory, depending on the account configuration. The possible fields in this
section are as follows: Email, Phone, First name, Last name, Primary Address,
Secondary Address, Zip Code, City, Country, State.

Merchant Console User Guide 140

Version 6.5 – February 2024
 • eWallet specific fields – Vendor (Freecharge; Amazon Pay; Phonepe).

10.Blacklists

We can blacklist a particular value for a merchant by making an ‘Add entry’. This means
that if the transaction data contains the data defined in the blacklist, the filter will be
triggered if added for the terminal. By using the blacklist filters fraudulent transactions
might be prevented from passing successfully through our gateway. Another function of
the “Blacklist” tool is to search in the blacklist database.

10.1. Blacklists

From the index page of the blacklist page, you could search for current entries in the
blacklist database. You can delete blacklist entries by first clicking on the “Actions”
button ( ) and then on the “Delete” button ( ). This action should be
done with caution. From the button “Export Files”, you can export the blacklist database
into a CSV or Excel file format.

Merchant Console User Guide 141

Version 6.5 – February 2024
Note: All PANs are shown as hashed due to the PCI DSS regulations.
You can search by:

• Name – This is the name of the particular blacklist type of entry, it can be: bin,
bin_name, bin_phone, card subtype, card type, country, email, first_name,
forwarded_ip, IBAN, last_name, mac_address, pan, pan_tail, password, phone,
region class, remote_ip, serial_number, session_id, ssn, user_id, user_level,
username.
• Value
• Date range From – To
• Merchant
• Masked PAN
• Terminal
• Created by
• Comment

*Note: Blacklist entries with comments which have a transaction ID associated are now
links and lead to the actual transaction.

10.2. Add Entries

Merchant Console User Guide 142

Version 6.5 – February 2024
From this tab of the Blacklists functionality, you can add new entries to it. All the entries
added will be tied to your available merchants or terminals.

The following fields are present for it:

• Name - This is the name of the particular blacklist type of entry, it can be: bin,
bin_name, bin_phone, card subtype, card type, country, email, first_name,
forwarded_ip, IBAN, last_name, mac_address, pan, pan_tail, password, phone,
region class, remote_ip, serial_number, session_id, ssn, user_id, user_level,
username.
• Value – This is the value of the particular entry; it depends on the type of entry
you have chosen to add.
• Comment – If you want to add any comment for later reviews.
• Blacklist Owner – Shows you a list with all available merchants/terminals –
select one to be an owner.

10.3. Stats

Shows a statistic of how many entries per entity are currently available in the blacklist
database.

Merchant Console User Guide 143

Version 6.5 – February 2024
10.4. Imports

You can import new entries into the blacklist database via file imports. This is very
helpful when you want to add a big number of new entries to the blacklist. First, click on
the “Browse” button and choose the file you want to import from your computer. After
you load the file click on the button “Upload Blacklists” to import the file entries.
The fields of the file must be separated using the character “;” (semicolon). The first line
of the file should contain a header with the name of the fields:

- Header: “type;owner_type;owner_id;name;value”

The next lines should contain the information of the entry that will be added to the
blacklist. Following are the possible values:

- Type: “w”
- Owner_type: “Merchant”
- Owner_id: the ID of the merchant entity. It can be found by going to the left-hand
menu Configuration -> Merchants and then choosing the appropriate merchant.
The table with the details that will be shown contains the ID.

Merchant Console User Guide 144

Version 6.5 – February 2024
 - Name: name of the blacklist filter that will be created, example: “country” or
“bin_country”. This will tell Genesis what field to compare against the blacklist.
- Value: the value that will be used to discern if a transaction should be stopped by
the blacklist filter.

A file with the information to be imported would look like this:

10.5. Export Files

From this tab, you can find and download any CSV or Excel exports of the blacklist
database you have made previously, so you do not have to re-generate and export them
again.

11.Whitelists

We can whitelist a particular value for a merchant by making an ‘Add entry’. By using
the whitelist, we can allow trusted cardholders to pass successfully through the gateway
while they are in the scope of a blacklist entry. Another function of the “Whitelists” tool
is to search in the whitelist database.

11.1. Whitelists

Merchant Console User Guide 145

Version 6.5 – February 2024
From the index page of the whitelists page, you can search for current entries in the
whitelists database. You can delete entries by first clicking on the “Actions” button (
) and then on the “Delete” button ( ). This action should be done with
caution. From the button “Export Files” you can export the whitelist database into a CSV
or Excel file format.

Note: All PANs are shown as hashed due to the PCI DSS regulations.

You can search by:

• Name – This is the name of the particular blacklist type of entry, it can be: bin,
bin_name, bin_phone, card subtype, card type, country, email, first_name,
forwarded_ip, IBAN, last_name, mac_address, pan, pan_tail, password, phone,
region class, remote_ip, serial_number, session_id, ssn, user_id, user_level,
username.
• Value
• Date range From – To
• Merchant
• Masked PAN

Merchant Console User Guide 146

Version 6.5 – February 2024
 • Terminal
• Created by
• Comment

11.2. Add Entries

From this tab of the Whitelists functionality, you can add new entries to it. All the entries
added will be tied to your available merchants or terminals. The following fields are
present for it:

• Name - This is the name of the particular whitelist type of entry, it can be: bin,
bin_name, bin_phone, country, email, first_name, forwarded_ip, last_name,
mac_address, pan, pan_tail, password, phone, remote_ip, serial_number,
session_id, ssn, user_id, user_level, username.
• Value – This is the value of the particular entry; it depends on the type of entry
you have chosen to add.
• Comment – If you want to add any comment for later reviews.
• Whitelist Owner – Shows you a list with all available merchants/terminals –
select one to be an owner.

11.3. Stats

Shows a statistic of how many entries per entity are currently available in the whitelist
database.

Merchant Console User Guide 147

Version 6.5 – February 2024
11.4. Imports

You can import new entries into the whitelist database via file imports. This is very
helpful when you want to add a big number of new entries to the whitelist. First, click on
the “Browse” button and choose the file you want to import from your computer, after
you load the file click on the button “Upload Blacklists” to import the file entries.

The fields of the file must be separated using the character “;” (semicolon). The first line
of the file should contain a header with the name of the fields:

- Header: “type;owner_type;owner_id;name;value”

The next lines should contain the information of the entry that will be added to the
whitelist. Following are the possible values:

- Type: “w”
- Owner_type: “Merchant”
- Owner_id: the ID of the merchant entity. It can be found by going to the left-hand
menu Configuration -> Merchants and then choosing the appropriate merchant.
The table with the details that will be shown contains the ID.

Merchant Console User Guide 148

Version 6.5 – February 2024
 - Name: name of the whitelist filter that will be created – example: “country” or
“bin_country”. This will tell Genesis what field to compare against the whitelist.
- Value: the value that will be used to discern if a transaction should be allowed by
the whitelist filter.

A file with the information to be imported would look like this:

11.5. Export Files

From this tab, you can find and download any CSV or Excel exports of the whitelist
database you have made previously, so you do not have to re-generate and export them
again.

12.Risk Management

This tab contains Chargebacks, Retrieval Requests, SAFE, TC40 that have been imported
into Genesis from Omnipay.

12.1. Chargebacks

The Chargebacks functionality gives you the ability to search for particular chargebacks
and filter the results by choosing different search criteria. You can export the found
chargeback data into CSV or Excel file formats by clicking on the button “Export Files”.
Search options:

• ARN
• Item type – this is the type of chargeback record: 1st chargeback, 2nd chargeback,
1st chargeback reversal, 2nd chargeback reversal, transfer reversal, re-
presentment, chargeback transfer to merchant acc, chargeback transfer to writeoff
account acq, chargeback to payment account retail.

Merchant Console User Guide 149

Version 6.5 – February 2024
 • Merchants
• Original transaction date From – To
• Post date From – To
• Import date From - To
• Add search filter – Reseller subtype, Reason code, Transaction ID

If you want to open a particular chargeback for more information, please click on the
Action>>View Details button.

12.2. Retrieval Requests

The Retrieval Requests functionality gives you the ability to search for particular
retrieval requests and filter the results by choosing different search criteria. You can
export the found retrieval requests data into CSV or Excel file formats by clicking on the
button “Export Files”.
Search options:

• ARN
• Merchants
• Original transaction date From – To
• Post date From – To
• Import date From - To
• Add search filter – Reseller subtype, Reason code, Transaction ID

Merchant Console User Guide 150

Version 6.5 – February 2024
If you want to open a particular chargeback for more information please click on the
Action>>View Details button.

12.3. SAFE

The SAFE functionality gives you the ability to search for particular fraud SAFE data
and filter the results by choosing different search criteria. You can export the found
retrieval requests data into CSV or Excel file formats by clicking on the button “Export
Files”.
Search options:

• ARN
• Merchant
• Fraud type – Lost, Stolen, Card Not Received as Issued, Fraudulent Application,
Issuer-Reported Counterfeit, Account Takeover, Card Not Present, Multiple
Imprint Fraud, Best-out Collusive Merchant, Acquirer-reported counterfeit
• Transaction date From – To
• Add search filter – Amount, Currency, Reseller subtype

Merchant Console User Guide 151

Version 6.5 – February 2024
12.4. TC40

The TC40 functionality gives you the ability to search for particular fraud TC40 data and
filter the results by choosing different search criteria. You can export the found retrieval
requests data into CSV or Excel file formats by clicking on the button “Export Files”.
Search options:

• ARN
• Merchant
• Fraud type – Lost, Stolen, Card Not Received as Issued, Fraudulent Application,
Issuer-Reported Counterfeit, Account Takeover, Card Not Present, Multiple
Imprint Fraud, Best-out Collusive Merchant, Acquirer-reported counterfeit
• Purchase date From – To
• Add search filter – Amount, Currency, Reseller subtype

Merchant Console User Guide 152

Version 6.5 – February 2024
 12.5. Export files

From this tab you can find and download any CSV or Excel exports of the blacklist
database you have made previously, so you don’t have to re-generate and export them
again.

13.Billing

After successful login, please navigate to “Billing” from the left menu panel. Under
Billing menu, you can find and export Interchange Details and PayCommerce Batches

13.1. Interchange Details

Interchange details could be filtered by various conditions – after expanding the Search
area search criteria could be applied.

Merchant Console User Guide 153

Version 6.5 – February 2024
 13.2. Paycommerce Batches

Paycommerce Batches details could be filtered by various conditions – after expanding

the Search:

You can click on “Show Transaction” to view Payment Transaction Details. By clicking
on “Toggle” you can see details of why the transaction has Failed.

13.3. Export Files

Filtered data from Interchange details could be exported both in CSV and xls format.
Generated files could be found and downloaded from the Export Files section under the
Billing menu.

14.Users

This is the section where we can edit, configure, and create more users to be able to
access the Merchant user consoles by certain procedures.
Once you log in to the Merchant console with administrative privilege you need to click
on the Users tab, and you will be redirected to the Users section.

Merchant Console User Guide 154

Version 6.5 – February 2024
The Merchant users tab provides options to add, edit, enable, or delete Merchant users.
From there, you can also see details such as: id, email, role, last login and create at.
Below is the Role-based access table, from where you can see which Roles and what
privileges are provided.
The procedure for creating new Merchant users is the following:

• Once you are on the Merchant users page simply click on the “New User” button

( )
• The Create user form is displayed.

• Here you need to fill in the required fields such as: Login, Email, First and Last
name
• Under the Role field, select the role that you want to apply for that user
• Under the Merchant field, select the Merchant to which this user will be assigned
• Select the Transaction types (Virtual Terminals) that you would like to have
enabled for the user
• Select if the user can make Exports or not.

Merchant Console User Guide 155

Version 6.5 – February 2024
The system will automatically send an email notification to the address that you have sent
under the Email field. The email contains an URL from which the user can enter his new
password for his new account.

• Two factor Authentication allows to enable 2FA for the user, which upon first log
in will be prompted to scan a QR code with a third-party authentication
application of their choosing.

Once the 2FA is activated for the user, upon every log in attempt the user will be
prompted to enter an OTP from the authentication application.

Merchant Console User Guide 156

Version 6.5 – February 2024
If the customer for some reason has disabled the account (didn’t log in for more than
three months) from the Admin users form you can simply enable it by clicking on the
padlock icon ( ) and the system will re-enable it. If you want to see more information
abour a particular user, you can navigate to the “Actions” button ( ) and then to
the “View Details” button ( ), and it will open a page from where you can see
how exactly the user was configured.

Merchant Console User Guide 157

Version 6.5 – February 2024
The “Edit” button is also available here, once you click on it you will be redirected to the
Edit User page.

The “Edit” button ( ) is available on the Users form as well under the “Actions”
button ( ), where you will also find the “Delete” function ( ).

Merchant Console User Guide 158

Version 6.5 – February 2024