The diagrams below show the way that PayVector's gateway platform works. This infrastructural design ensures to provide merchants as near to 100% uptime as is possible. This will take into account the Merchant's ability to communicate with the Gateway through public network systems outside of the control of either the Merchant or PayVector, i.e. a transit peering problem on the public Internet.

In the case of a public network failure outside the control of either PayVector or a Merchant, we supply pre‐written code packs in all the common development languages that deal with large scale Internet failures, i.e. two major peering providers losing connectivity.

The diagram above shows how PayVector ensures that merchants never experience a single point of failure. The merchant can connect to either Cluster 1 or Cluster 2. In the event that Cluster 1 fails for whatever reason, the transactions can be redirected to Cluster 2. Therefore, the merchant does not experience downtime and continues taking transactions as usual.

The diagram above shows how the transactions reach the database. You can also see that the payment gateway and the merchant management system (MMS) are separate and therefore giving you the flexibility of choosing to have a fully hosted white label system by PayVector, or to incorporate part of the technology into your existing systems.