🔐 Required Role Permissions: Gateways
Create Gateway
In the Ventrata dashboard, go to Supplier Settings > Gateways.
Gateways
Select the desired gateway type.
On the left side of the form, enter a name for the gateway.
The 'Active' checkbox must be selected for the gateway to be used in the defined areas, see step 8.
Gateway Name
Select what currencies can be used to make payments through this gateway.
Currencies
📒 NOTE
The list of currencies comes from the currencies selected in the supplier settings.
If you want to enable fraud tools for this gateway, check the 'Fraud Assessment Required' box.
Fraud Assessment Required
📒 NOTE
When fraud assessment is enabled, multiple checks are performed on each transaction that contribute to a fraud score. This score identifies potentially fraudulent transactions and may increase the number of declined transactions.
Apply a fee (a % of the total price) for, for example, credit card transactions or bank transfers.
Surcharge
Check the 'Custom Gateway' box if your gateway is outside of the standard Ventrata integration.
Custom Gateway
📒 NOTE
For more information, please contact your Ventrata Customer Successive Representative.
Select the sources where the gateway will be used to process payments:
E-commerce - used by customers on the web checkout
MOTO - used by internal sellers and reseller agents on the sales portal
Point of Sale - used by internal sellers and reseller agents on the Ventrata terminal app
Sources
Select specific areas where the gateway will be used to process payments:
Destinations, Checkouts & Portals
📒 NOTE
Make sure that the appropriate gateways are also selected on the specific destination, checkout and portal.
The right half of the gateway form is different for each gateway, see below. Work with your dedicated Ventrata Payment Specialist or Customer Success Representative to complete the form.
When ready, press the Create Gateway button.
Create Gateway
List of Fields for Selected Gateways
Adyen
Adyen
Adyen
Field | Description |
Merchant Account | The name of the merchant account you want to link to this gateway, as entered in the Adyen Customer Area. |
Live URL Prefix | Ensures that transactions are routed correctly to your Adyen environment. Navigate to Developers > API URLs > Prefix to Get Live URL Prefix |
Require Holder Name | The customer must enter the card or account holder's name during checkout. |
Require Billing Address | The customer must provide their billing address during checkout. |
API Key | A unique identifier used for authentication, ensuring secure communication between Ventrata and Adyen. |
Terminal API Key | A secure key used to process payments, issue refunds, collect customer information, and perform other interactions on Adyen-supplier payment terminals. |
API Client Key | A public key used for client-side authentication. It allows Adyen to verify that requests made from Ventrata are legitimate and authorised. |
Report User | Username of the report user in your Adyen Customer Area, used for downloading reports via API. |
Report Password | The passowrd (Basic Authentication token) generated in the Adyen Customer Area to authenticate the report user for report downloads. |
Print Customer Receipt | Generate and print a receipt for the customer. |
Printer Merchant Receipt | Generate and print a merchant copy of the receipt for records keeping. |
Allowed Payment Brands | Select which QR code-based payment methods your POS terminal should accept. |
Ventrata Adyen
Ventrata Adyen
Ventrata Adyen
Field | Description |
Merchant Account | The name of the merchant account you want to link to this gateway, as entered in the Adyen Customer Area. |
Require Holder Name | The customer must enter the card or account holder's name during checkout. |
Require Billing Address | The customer must provide their billing address during checkout. |
Print Customer Receipt | Generate and print a receipt for the customer. |
Printer Merchant Receipt | Generate and print a merchant copy of the receipt for records keeping. |
Allowed Payment Brands | Select which QR code-based payment methods your POS terminal should accept. |
VivaWallet
VivaWallet
VivaWallet
Field | Description |
Currency | Must match the currency configured in your VivaWallet account. |
Demo Account | Indicates whether you are connecting to a VivaWallet demo account. |
Merchant ID | A unique identifier for your VivaWallet account. In your VivaWallet account, navigate to Settings > API Access. |
API Key | Used to authenticate API requests with VivaWallet. In your VivaWallet account, navigate to Settings > API Access to get your key. |
Native Checkout Client ID | A unique identifier for your native checkout, used to process payments. |
Native Checkout Client Secret | Used to authenticate payments made through your native checkout. |
Smart Checkout Client ID | A unique identifier for Smart Checkout, VivaWallet's online a payment gateway for e-commerce platforms. In your VivaWallet account, navigate to Settings > API Access to retrieve this ID. |
Smart Checkout Client Secret | Used to authenticate your application with the Smart Checkout payment gateway In your VivaWallet account, navigate to Settings > API Access to get this key. |
Source Code | A four-digit code that identifies a specific payment source in your VivaWallet account. In your VivaWallet account, navigate to Sales > Online Payments > Website Apps to find your Source Code. |
Print Customer Receipt | Generate and print a receipts for the customer. |
Printer Merchant Receipt | Generate and print a merchant copy of the receipt for records keeping. |
Order Gateways
On the Gateways table, grab the left-most part of each row and reorder your existing gateways in the order in which they will be used on the
sources,
currencies,
destinations,
checkouts,
and portals
the gateway supports, see Create Gateway above.
Reorder Gateways
📒 NOTE
The order in which gateways are listed does not affect how locations and terminals only use gateways. Locations and terminals also ignore whether the gateway is 'active' and the sources selected.
Locations and terminals use the gateway selected in the location and terminal forms, respectively.