Skip to main content

Field Recommendation

The Field Recommendation engine determines which identity fields should be requested during an identity exchange, based on the specific regulatory requirements of the transaction.

Why Field Recommendation Matters​

Different regulations require different identity fields:

  • FATF Travel Rule requires originator and beneficiary name, account number, and address
  • MiCA requires distributed ledger address and unique transaction identifier
  • Some jurisdictions require additional fields (date of birth, national ID)

Rather than requesting all possible fields every time (over-collection) or missing required fields (non-compliance), the Field Recommendation engine optimizes the request to include exactly what is needed.

How It Works​

  1. Transaction analyzed — Jurisdictions, amount, asset type, and counterparty status are evaluated
  2. Regulation mapped — Applicable regulations identified for both sender and receiver jurisdictions
  3. Field set computed — The minimum required set of identity fields is determined
  4. Recommendation returned — Oracle uses this field set in the identity exchange request

Benefits​

  • Data minimization — Only collect what regulation requires
  • Compliance completeness — Never miss a required field
  • Efficiency — Reduces back-and-forth between counterparties
  • Jurisdiction-aware — Automatically adapts to cross-border requirements