Tap Payments Extension

Installation

Preliminary Works

The following information is requested from the provider for the brand-specific and production (live) environment.

• API_URL
• API_MERCHANT_ID
• API_SECRET_KEY

A hash_key of at least 32 characters in length and a secret_key of at least 41 characters in length should be generated. The keys produced during the installation must be stored. Here is an example command to generate a random key:

openssl rand -base64 41

Environment Variables

The extension installed to the relevant project in ACC must have the following environment variables. Environment variables can be entered before or after the deployment phase. As changes are made to the environment variables, the deployment process must be performed again.

Variable	Description
SECRET_KEY	Code received during the preliminary works phase
ADMIN_USERNAME	A username can be entered (example: ‘akinon’)
ADMIN_PASSWORD	A newly created and extension-specific strong password
ADMIN_EMAIL	The e-mail address of the installer can be entered
HASH_KEY	Code received during the preliminary works phase
WEBHOOK_URL	https://{SHOP_URL}/orders/hooks/payment
API_URL	API URL received during the preliminary works phase (without a trailing slash at the end)
API_MERCHANT_ID	API MERCHANT ID received during the preliminary works phase
API_SECRET_KEY	API SECRET KEY received during the preliminary works phase
AUTO_TYPE	Desired Auto Type (VOID/CAPTURE) Default:VOID
AUTO_DURATION	Desired Auto Duration in Hours Default:100
PAYMENT_SOURCE	The source of the payment method. Example:KNET Note: Before using a different payment source, please contact the PAT team.

Omnitron Settings

The installed extension must also be defined to the project via Omnitron. This can be done on the Payment Options & Add/Edit POS Integration pages. After the settings are completed, it will be accessible under a new tab on the payment screen as it is a redirection type payment integration.

Payment Options

One payment option must be defined in Omnitron to be specific for the extension installed. Explanations on how the settings should be made at this stage are in the table below.

Field	Description
Payment Option	Redirect to bank
Payment Option Name	Tap Payment Extension
Payment Option Slug	tap_extension
Config	{"pos_slug":"tap_extension"}

POS Integration

One POS integration must be defined in Omnitron to be specific for the extension installed. Explanations on how the settings should be made at this stage are in the table below.

Field	Description
Name	Tap Payment Extension
Slug	tap_extension
Gateway	extension
Resource URL	EXTENSION URL
Username	ADMIN_USERNAME value in environment variables
Password	ADMIN_PASSWORD value in environment variables
Payment Type	AUTH