To maximise platform availability, Ravelin operates a global load balancer for the 3-D Secure (3DS) API endpoints.
We have a European cluster hosted in Belgium and a US cluster hosted in Iowa.
The diagram below shows the relationship between our global and regional load balancers.
If you direct requests to the global load balancer, requests will be routed to the nearest geographical cluster where data will be temporarily stored over the lifetime of a 3DS transaction. In the unlikely event of a regional failure the global load balancer will route traffic to the another available cluster.
If you are governed by strict data location policies you may opt to use one of our regional load balancers. This will guarantee that your data will remain in the same geographical location, however you will be not protected from a regional cluster failure.
The table below shows the different hostnames to use when calling the 3DS API depending on your data policies.
| Cluster | Original 3DS API | Global 3DS API | Regional 3DS API |
|---|---|---|---|
| Belgium (EU) | https://pci.ravelin.com/3ds/* | https://3ds.live.pci.ravelin.com/3ds/* | https://3ds-europe-west1.live.pci.ravelin.com/3ds/* |
| Iowa (US) | N/A | https://3ds.live.pci.ravelin.com/3ds/* | https://3ds-us-central1.live.pci.ravelin.com/3ds/* |
If you are sending PCI data to Ravelin then you should continue to use the existing hostname.
The change in hostnames is specific to Ravelin 3DS EU clients and does not affect any other Ravelin products.
Was this page helpful?