Account Takeover Integration

Testing Your Integration

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.

Force Specific Recommendations

You should ensure that you are listening to the action that Ravelin returns, and handling it appropriately.

Set the login.username field to an email address using one of the following three email domains to force a specific action from the Login (v3) endpoint.

Email Domain Action
@qa-force-ato-permit.com PERMIT
@qa-force-ato-warn.com WARN
@qa-force-ato-block.com BLOCK

These values will only work in your sandbox account.

Simulating Slow Networks

Networks are inherently unreliable. Your system should be robust against slow responses from the network and from Ravelin.

Send the Ravelin-Min-Latency header, with the specified delay in milliseconds to force requests you make to 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.

Feedback

© Ravelin Technology Ltd. All rights reserved