Bank Terminal

A bank terminal represents a connection to a payment provider that processes transactions. You configure its provider, currency, credentials, and 3DS behavior, then add it to a route inside a blueprint so transactions can be sent through it.

Before you begin

• You have access to the Entities → Bank Terminals section of the console.
• You know which provider this terminal connects to — the provider can’t be changed after creation.
• You have the provider’s credentials and parameters on hand, since the terminal’s attributes are set from them.

Create a bank terminal

1. Open Entities → Bank Terminals and select Create Bank Terminal in the top-right corner.

   

2. Fill in the terminal fields (see Bank terminal fields below).

3. Select Create Bank Terminal in the bottom-right corner.

4. You’re redirected to your new terminal’s page, where you can configure its attributes and add it to a route.

   

Bank terminal fields

Field	Required	What to enter
Name	Yes	A name for the terminal. Must be unique across all bank terminals.
Bank Terminal description	No	An optional description of the terminal.
Status	Yes	Enabled or Disabled.
3DS Secure	Yes	Enable or disable 3DS Secure for this terminal.
Descriptor	No	The text shown to the merchant in the Descriptor field.
Provider	Yes	The payment provider this terminal connects to.
Channel	No	Configure the channel — used when you have multiple bank terminals.
Currency	Yes	The terminal’s currency, selected from the list.

Caution

Choose the provider carefully. After the bank terminal is created, the provider can’t be changed — you’d need to create a new terminal.

Edit or copy a bank terminal

On the terminal page, use the buttons in the top-right corner:

• Edit — change the terminal’s settings.
• Copy — duplicate its settings to create a new terminal.

Restrictions

The Restrictions section filters incoming requests to this terminal. These filters are used by your Route in the Blueprints section.

Configure attributes

Open the Attributes section on the terminal page and fill in each group.

Note

Attribute values are set based on your provider’s parameters.

The attribute groups are:

1. 3DS options

   

2. Credentials

   

3. Currency Conversion

   

4. Options

   

5. Recurrents Configuration

   

6. URL Configuration

   

Add the terminal to a route

You add a bank terminal to a route through a cascade in the route rule.

1. In the Route Rule section, select Create Cascade.

   

2. Choose the cascade type (see Cascade types below).

3. Select Create Cascade in the bottom-right corner.

4. In the cascade section, select Add Terminal.

   

5. Select your terminal from the list. It’s added to the Route.

Cascade types

The cascade type controls how transactions are distributed across terminals.

Group	Type	How it distributes
By Coefficient	Transaction Amount	Sorts transactions across terminals by amount, using the probability percentage you set.
By Coefficient	Transaction Count	Sorts transactions across terminals by transaction count, using the probability percentage you set.
Equals ON	Transaction Amount	Distributes evenly by amount, with an equal probability percentage across terminals.
Equals ON	Transaction Count	Distributes evenly by transaction count, with an equal probability percentage across terminals.
Chain BY	Coefficient by Transaction Count	Chains terminals by count using your probability percentages. Filtered or over-limit terminals are excluded, then a chain is formed from the rest by coefficient.
Chain BY	Equivalently on Transaction Count	Chains terminals by count with an equal probability percentage. Filtered or over-limit terminals are excluded, then a chain is formed from the rest.
Chain BY	Sequence	Chains terminals in a fixed cascading order.
Other	First in Sequence	Selects the first suitable terminal for each transaction.

Troubleshooting

Problem	What to do
Create Bank Terminal stays inactive	Check the required fields — a unique name, a selected provider, and a currency.
The terminal name is rejected	Names must be unique across all bank terminals — choose a different one.
You selected the wrong provider	The provider can’t be changed after creation. Create a new terminal — use Copy to reuse the other settings.
Attribute values don’t behave as expected	Attribute values come from your provider’s parameters — verify them with the provider.