Our platform has been designed to be resilient to failure. However, in the unlikely event of an error we will attempt to continue to process your request as completely as possible.
When requesting a transaction optimisation recommendation you also have to request a fraud recommendation, which means errors could occur in the different parts of our platform.
If an error occurs when generating a transaction optimisation recommendation, but not during fraud scoring, we will still return a payment fraud recommendation. A message will be returned describing the error which occurred during transaction optimisation.
An example error response is shown below:
{
"status": 200,
"message": "could not generate transaction optimisation recommendation: the transaction is completed",
"timestamp": 17381626600,
"data": {
"customerId": "134cc0c0-7bcc-480a-9363-622689121fd4",
"action": "ALLOW",
"score": 54,
"source": "RAVELIN",
"scoreId": "6849a141-89c9-4f18-a07a-40dd928f8dbf"
}
}If an error occurs during fraud scoring we will not be able to return a transaction optimisation recommendation and will return the corresponding HTTP status. See API Reference Errors for more details.
For guidance on how to best respond to error codes, please consult our Error Handling documentation or contact a Ravelin engineer.
Test your transaction optimisation integration
Was this page helpful?