Payment terminals
Adyen
An Adyen payment terminal requires you to configure it in Adyen's own dashboard, as well as with a few settings in EVA.
| Field | Description |
|---|---|
| Name | Whatever you want. |
| Device backend ID | Whatever you want. |
| Device type | Pin |
| ECRID | Your device model, a '-', followed by its serial number with no dashes in the numbers, e.g. P400Plus-123456789 |
We advise to either use fixed/manual IP addresses for your Adyen payment terminals or to make use of DHCP reservation. This will enable the devices to offer more reliable Local PIN payment functionality. These devices need to be in the same network as your Watchtower.
In the same vein we also advise each terminal having its own external connection.
Stripe
A Stripe payment terminal requires you to register your reader (terminal) in Stripe's own dashboard and to specify a few settings in EVA.
| Field | Description |
|---|---|
| Name | Whatever you want. |
| Device backend ID | Whatever you want. |
| Device type | Pin |
| ECRID | Your terminal's Reader ID, e.g. 123-456-789 |
PayOne
A PayOne payment terminal requires you to register your reader (terminal) in PayOne's own dashboard and to specify a few settings in EVA.
| Field | Description |
|---|---|
| Name | Whatever you want. |
| Device backend ID | Whatever you want. |
| Device type | Pin |
| IP address | tcp://TerminalIP:Port - e.g.: tcp://192.168.225.47:20007 |
Your TerminalIP and Port can be found on the terminal itself.
Verifone
A Verifone payment terminal requires you to register your reader (terminal) in Verifone's own dashboard and to specify a few settings in EVA.
| Field | Description |
|---|---|
| Name | Whatever you want. |
| Device backend ID | Whatever you want. |
| Device type | Pin |
| ECRID | Device Serial ID as found in your Verifone cloud environment |