Integration Use Case

There are two ways to get your transactions into Transaction Monitoring. Choose the one that matches what you already run with TrustVision.

Option 1: Face Authentication or Behavioral BiometricsOption 2: Standalone integration
Best whenYou already authenticate or score users with TrustVisionYou do not use those products, or you want to screen events on their own
What you changeAdd transaction_data to a call you already makeSend your events to Transaction Monitoring from your backend

Option 1: Pass transaction_data with Face Authentication or Behavioral Biometrics

If your platform already uses TrustVision Face Authentication or Behavioral Biometrics, send the payment context in the optional transaction_data object of the call you already make. It is purely additive: leave it out and the request and its result stay exactly as they are today. Every field inside it is optional, so send the ones you have.

ProductCall you already makeWhere transaction_data goes
Face AuthenticationAuthenticate — POST /v1/face_authA top-level field of the Authenticate request
Behavioral BiometricsCompute a behavior score — POST /v1/behavior/scoreA top-level field next to challenge_id

Face Authentication

Add transaction_data to the Authenticate request, alongside the face and auth_type you already send.

JSON
{
    "cus_user_id": "customer-001",
    "auth_type": "transfer",
    "selfie_type": "passive",
    "faces": [{ "id": "5f0e9dbe-1e0f-4bd7-9e39-5f0b8ba4c9d1" }],
    "transaction_data": {
        "transaction_id": "txn-001",
        "transaction_timestamp": "2024-01-15T10:30:00Z",
        "transaction_amount": 5000000,
        "currency_code": "VND",
        "transaction_type": "transfer",
        "channel": "mobile_app",
        "beneficiary_account_number": "0987654321",
        "is_new_beneficiary": true
    }
}
  • The object is read only when face authentication policy checks are enabled for your account. With those checks off it is accepted and ignored.
  • It is meaningful only on Authenticate. Register a face accepts the field but does not evaluate or store it.

The full field list is in Transaction data on the Authenticate page.

Behavioral Biometrics

After the app finishes collecting, your backend calls Compute a behavior score with the session's challenge_id and the transaction context.

JSON
{
    "challenge_id": "d4e5f6a7-b8c9-0123-4567-89abcdef0123",
    "transaction_data": {
        "transaction_id": "txn-001",
        "transaction_timestamp": "2024-01-15T10:30:00Z",
        "transaction_amount": 5000000,
        "currency_code": "VND",
        "transaction_type": "transfer",
        "channel": "mobile_app",
        "beneficiary_account_number": "0987654321"
    }
}

When the behavior policy check is enabled for your account, the response also carries the recommended action in decision.final_action. The full field list is in Transaction data on the Compute a behavior score page, and the end-to-end sequence is in the Behavioral integration flow.

Option 2: Integrate through the standalone API

If you do not use Face Authentication or Behavioral Biometrics, or you want to screen events independently of an authentication, you can integrate Transaction Monitoring on its own. Your platform sends its transaction events straight to Transaction Monitoring through the standalone API, without going through a TrustVision authentication call.

Other integration methods, such as a message queue, are also supported. Contact your account manager for advice on the approach that fits your architecture and volume.