As with all software, it’s important to get it working, and then keep it working. Ravelin has multiple features to aid you in testing your integration. To ensure safe usage, the below features are only enabled for sandbox accounts.
You should ensure that you are listening to the action that Ravelin returns, and handling it appropriately. By default, a Payment Fraud action can be forced by using a customer email with the following email domains:
Networks are inherently unreliable. Your system should be robust against slow responses from the network, and from Ravelin.
Ravelin-Min-Latency header, with the specified delay in milliseconds will ensure that all requests you make will take at least the specified duration in milliseconds on Ravelin’s servers. This can be used to test your system’s behaviour when an abnormal increase in network latency, or Ravelin’s latency occurs.
If you run tests against your live infrastructure, and these send fraud data to Ravelin, then it’s very easy to run into trouble with fraud networks.
Here are some things to consider to avoid this.
Was this page helpful?