API endpoint / API reference

Screen a transaction

Submit transaction and customer context to the private-preview screening contract and retain the structured decision evidence.

StatusPrivate preview
AudienceBackend engineering, AML operations
OwnerUWAY Engineering
Reviewed2026-08-02

Endpoint

POST/v1/screen/transactionPrivate preview

Submit transaction, customer, counterparty, and Travel Rule context for a configured screening decision. The fields enabled for a tenant depend on the implementation contract.

Request

curl -X POST "https://TENANT_BASE_URL/v1/screen/transaction" \
  -H "Authorization: Bearer YOUR_TENANT_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: txn_8f72b1c4e5d9" \
  -d '{
    "transaction_id": "txn_8f72b1c4e5d9",
    "sender": {"id": "cus_sender_01", "entity_type": "individual"},
    "recipient": {"id": "cus_recipient_01", "entity_type": "individual"},
    "amount": {"value": "50000.00", "currency": "USDT"},
    "network": "ethereum",
    "travel_rule": {"required": true}
  }'

Request fields

FieldTypeRequirementPurpose
transaction_idstringRequiredStable business identifier used across decisions and evidence
senderobjectRequiredOriginating party reference and permitted context
recipientobjectRequiredBeneficiary or counterparty reference and permitted context
amountobjectRequiredDecimal value as a string plus asset or currency
networkstringConditionalNetwork or rail used by the transaction
travel_ruleobjectConditionalApplicability and exchange context

Example response

{
  "transaction_id": "txn_8f72b1c4e5d9",
  "uway_reference": "scr_7d3a91c2",
  "status": "review",
  "risk_level": "medium",
  "reason_codes": ["COUNTERPARTY_CONTEXT_REQUIRED"],
  "evidence_refs": ["ev_14f2"],
  "policy_version": "tenant-policy-2026-08"
}

Handling the response

Persist the business identifier, UWAY reference, status, reason codes, evidence references, and policy version before taking an irreversible action. A synchronous response may be followed by a webhook if analyst review or partner exchange changes the case.

Failure handling

  • Retry network timeouts with the same idempotency key.
  • Do not treat an HTTP or parsing failure as an approved transaction.
  • Route unavailable or incomplete decisions according to the institution's degraded-service policy.
  • Preserve the error code and correlation reference for support and audit.