v1

latestOpenAPI 3.0.32026-07-24148824715.6 KB
Transactions

Create and process a transaction

Creates a transaction and executes our payment screening and transaction monitoring processes. The response will indicate whether the transaction should be held or processed. Updates a transaction if a transaction with the same external_identifier, occurred_at, customer_external_identifier and details.type already exists but other data has changed. Supports updating existing transactions on the Synchronous Transaction Monitoring flow only; not supported for fast payment screening or async flows. This endpoint requires PAYMENT_SCREENING_BASE and/or TRANSACTION_MONITORING_BASE account permission depending on the configuration identifies supplied with the payload.

post/v3/transactions/process

Request body

scenario_configuration_identifiersstring[] nullable

The list of scenario configurations the transaction should be monitored against.

screening_configuration_identifierstring uuid nullable

The configuration identifier to be used to screening the transaction.

Response

Transaction successfully processed

Example response

{
  "evaluation_result": {
    "errors": [
      {
        "detail": "Missing field value: transaction_identifier",
        "title": "Input Validation Error"
      }
    ],
    "scenario_evaluations": [
      {
        "results": [
          {
            "error": {
              "detail": "Missing field value: transaction_identifier",
              "title": "Input Validation Error"
            },
            "outcome": "ALLOW",
            "scenario_identifier": "e15352e0-b707-4d0b-a526-2a1092202ad4",
            "scenario_name": "Payment Limit - Outbound"
          }
        ]
      }
    ],
    "screening_evaluation_results": {
      "error": {
        "detail": "Missing field value: transaction_identifier",
        "title": "Input Validation Error"
      }
    }
  }
}