Cloud ECR (legacy)
Our new multicore platform incorporates a network of TGU platforms, each equipped with dedicated PIN servers for instore transaction processing. Within this ecosystem, a TGU maintains awareness of terminals residing on other TGU platforms through the Global Management System acting as a central message broker.
This is a legacy support page, please use the cloudconnect setup via CCV or PAY.POS terminals
Currently, we have the following dedicated PIN platforms:
| TGU | Pin location |
|---|---|
| pay.nl | pin.pay.nl, instore.pay.nl |
| achterelkebetaling.nl | pin.achterelkebetaling.nl |
| payments.nl | pin.payments.nl |
Outage handling
In the event of a GMS outage, the communication between TGU platforms regarding terminal locations is interrupted. This situation can become challenging if you have to transfer your terminal from Core A to Core B during the outage. If it becomes necessary for you to switch the platform of your terminal while the GMS is down, you must start a transaction for that terminal on the specific TGU platform to which the terminal is directly linked.
For example, if you have a terminal located at pin.pay.nl and the data center behind pay.nl experiences an outage, you can switch your terminal to another TGU, such as payments.nl. However, only the TGU behind payments.nl will be aware of this terminal's new location. Achterelkebetaling.nl will not be informed of the terminal's relocation until the GMS is back online and has recovered it's interrupted processes.
A schematic overview of the interconnectability of a terminal between the TGU platform's.
Network connection quality
Please keep in mind that a stable network connection is essential. CloudConnect maintains a permanent connection between the terminal and our systems. If the connection is lost or experiences high latency, the terminal may temporarily become unresponsive or enter an unstable state.