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. To ensure safe usage, the below features are only enabled for sandbox accounts.

Forcing a specific action

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:

• @qa-force-allow.com → ALLOW
• @qa-force-review.com → REVIEW
• @qa-force-prevent.com → PREVENT

Simulating slow networks

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

Sending the 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.

Test accounts and networks

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.

• If possible, don’t send test data to Ravelin.
• Never sign in to a test account with a personal device.
• Never use real phone numbers or email addresses in test data.
• Please use account names that are easily identified as test accounts. If something does go wrong it will be much easier for us to unpick it for you if we can identify which data is test data.
• If possible tag test accounts as “QA” in the Ravelin dashboard.

Next steps

Ensure you’re handling errors correctly

Get ready to go live with payment fraud recommendations

Feedback

Was this page helpful?

Thanks for the feedback. If you'd like to provide more detail you can share it in our Help Center.