Skip to main content

Fraud and continuous assurance

Initial onboarding is a point in time. Assayra can continue evaluating transactions, identity freshness and step-up requirements without rebuilding the original application.

Transaction fraud​

Submit an account/transaction event with a fraud:write key and unique idempotency key. The versioned rules evaluate signals such as:

  • value and velocity;
  • threshold structuring;
  • rapid duplicate activity;
  • shared or changed device;
  • identity/account state; and
  • geography or corridor risk.

The response is allow, review or block with an explainable score, rule IDs/versions and evidence references. Review/block results create an alert and can create a linked investigator case.

Example event​

{
  "eventId": "txn_018f65c6",
  "applicationId": "app_…",
  "accountReference": "acct_845901",
  "amountMinor": 275000,
  "currency": "SGD",
  "occurredAt": "2026-07-21T10:05:00.000Z",
  "counterpartyCountry": "GB",
  "deviceReference": "device_e8f…"
}

Do not send raw device fingerprints if a stable pseudonymous reference is sufficient.

Continuous assurance​

Continuous assurance tracks freshness of identity, document, screening, device and other required signals. Policies can issue a step-up when assurance falls below the required level.

Examples:

  • document expiry approaches;
  • sanctions data or screening becomes stale;
  • account recovery changes the trusted device;
  • transaction risk requires stronger presence; or
  • customer circumstances trigger new ECDD evidence.

Step-up journey​

A step-up uses a new, scoped credential and explicit purpose. Completion updates the freshness ledger and emits an event; it does not rewrite the original evidence or decision receipt.