Post Transaction Monitoring Request

The Transaction Monitoring API endpoint processes transactions in real-time, calculating the fraud percentage based on your predefined thresholds and limits. This endpoint allows for detailed monitoring of transactions to detect and flag potentially fraudulent activity. All fields in the request are required to ensure a comprehensive assessment, and each transaction’s reference field must be unique for accurate tracking.

Request Endpoint

POST: {{BASE_URL}}/api/v1/monitoring/transaction_monitoring/

  • Media-Type: application/json

Status Codes

  • 201 Created: Transaction processed successfully.
  • 400 Bad Request: Missing or invalid fields in the request.
  • 500 Internal Server Error: Unexpected error during processing. The request body is not set correctly.

Suspicious Activity Codes:

  • 450 - Suspicious Transaction Detected (Requires Manual Review)
  • 451 - High-Risk Transaction (Potential Fraud)
  • 452 - Unusual Transaction Behavior (Pattern Anomaly)
  • 453 - Velocity Check Failed (Too Many Transactions in Short Time)
  • 454 - Geographic Inconsistency (Unusual Location)
  • 455 - Transaction Amount Too High (Above Threshold)
  • 456 - Blacklisted Account or Entity
  • 457 - Repeated Failed Transactions (Possible Fraud Attempt)

Safe Activity code

  • 200 - Transaction Approved (No Issues)
  • 201 - Transaction Successfully Processed (Created)
  • 202 - Transaction Pending Review (Routine Check, No Immediate Risk)
  • 210 - Trusted Transaction (Verified and Safe)
  • 211 - Low-Risk Transaction (No Anomalies Detected)
  • 212 - Recurring Transaction Approved (Previously Authorized Pattern)
  • 220 - Whitelisted Entity (Pre-approved Account or Business)
  • 221 - Known Customer (Transaction Aligns with User History)

Payload Example Request

{
  "transaction_id": "18772",
  "amount": 1500.00,
  "currency": "USD",
  "transaction_type": "transfer",
  "account_type": "corporate", //individual or corporate
  "status": "completed",
  "origin_account": {
    "account_number": "9876543210",
    "bank_code": "001"
  },
  "destination_account": {
    "account_number": "0123456789",
    "bank_code": "002"
  },
  "customer_details": {
    "customer_name": "Jane Doe",
    "customer_email": "jane.doe@example.com"
  },
  "additional_info": {
    "ip_address": "192.168.1.1",
    "location": "San Francisco, CA", //"lat=-30.6556,lon=-65.7655"
    "transaction_description": "Payment for order #789"
  }
}

201 Created Response

{
    "status": "Success",
    "data": {
        "activity_code": "200"
        "status": "completed",
        "comment": []
    },
    "message": "Transaction was successfully processed"
}

Request Body

FieldDescriptionType
transaction_idThis is the unique identifier for the transactionString
amountThe transaction amountFloat
currencyThis is transaction currency (e.g., USD, NGN)String
transaction_typeType of the transaction (e.g., transfer, card)String
account_typeAccount type associated with the transaction (individual or corporate)String
statusStatus of the transaction (e.g., completed, pending)String
origin_accountDetails of the originating accountObject
- account_numberAccount number of the originating accountString
- bank_codeBank code of the originating accountString
destination_accountDetails of the destination accountObject
- account_numberAccount number of the destination accountString
- bank_codeBank code of the destination accountString
customer_detailsInformation about the verified customer initiating the transaction.Object
- customer_nameCustomer’s full nameString
- customer_emailCustomer’s email addressString
additional_infoAdditional details regarding the transactionObject
- ip_addressIP address of the customer during the transactionString
- locationCustomer’s location (can be formatted as “lat=-30.6556,lon=-65.7655”)String
- transaction_descriptionDescription of the transaction (e.g., Payment for order #789)String