Transaction Optimisation Integration

Error handling

Our platform has been designed for resilience. However, in the unlikely event that an error is returned, we will attempt to continue processing your request as best as possible.

When requesting a transaction optimisation recommendation, you also have to request a payment fraud recommendation. This means that an error could occur on 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. An error will be returned for transaction optimisation.

{
  "status": 200,
  "timestamp": 1710864095668,
  "data": {
    "action": "ALLOW",
    "transactionId": "64dfcd76-934c-48af-896e-f31137b59b10",
    "scoreId": "7fffffff9a064920016f15189-3905fa8f-ef1c-4fa4-918c-da1e9a3ad0ff",
    "score": 0.765,
    "rules": {}
  },
  "message": "could not generate a transaction optimisation recommendation: the transaction step has an invalid type"
}

If an error occurs during payment fraud scoring, we will not be able to return a transaction optimisation recommendation and will return the corresponding HTTP status. See our payment fraud error handling page for more details.

Next steps

Test your transaction optimisation integration

Feedback