Skip to content

Transaction entity

Generate coherent financial transactions with amount, party, channel, status, and location data.

Why: Use Transaction for financial scenarios where amount, currency, parties, channel, status, time, and location must form one coherent event; compose fields manually to test invalid combinations.

1
<variable name="value" entity="Transaction"/>

Output: Typed Transaction value.

Parameters

  • dataset: str | null; Default None — Country dataset controlling currency, parties, and location conventions.

Attributes

  • account (BankAccount | None): Associated bank account, when linked.
  • amount (float): Transaction amount.
  • channel (str): Transaction channel, such as online or POS.
  • currency (str): ISO 4217 currency code.
  • currency_symbol (str): Currency symbol.
  • description (str): Transaction description.
  • direction (str): Transaction direction, such as debit or credit.
  • is_international (bool): Whether the transaction crosses borders.
  • location (str): Transaction location.
  • merchant_category (str): Merchant category.
  • merchant_name (str): Merchant name.
  • reference_number (str): Reference number.
  • status (str): Transaction status.
  • transaction_date (datetime): Transaction timestamp.
  • transaction_id (str): Synthetic transaction identifier.
  • transaction_type (str): Transaction type.

Limits

The available attributes and values depend on the registered entity, its dataset, and its documented constructor options.