Skip to main content
Use Midaz Module to view, create, and monitor Transactions through a visual interface. The Transactions page provides a centralized view of all financial movements in your Ledger, allowing you to track balances, verify operations, and create new transactions without writing code.
For technical details about transaction structures, double-entry accounting, N:N transactions, and API integration, see the Transactions reference documentation.

​
Accessing the Transactions page

To open the Transactions page, select the Transactions option from the left-side menu. The Transactions page displays a table listing all Transactions in your Ledger.
If you do not have any Transactions, the list will appear empty with a prompt to create your first transaction.

​
Available actions

From the Transactions page, you can:

Create a Transaction

Record a new asset movement between accounts

Check Transaction details

See complete transaction information and operations

​
Transaction status

Transactions in Midaz have the following statuses:
  • APPROVED - Transaction was successfully processed and recorded
  • CANCELED - Transaction was canceled (if cancellation is supported)
Once a transaction is approved, it cannot be modified or deleted. This ensures the integrity of your financial records.

​
Common use cases

A basic transaction moving funds from one account to another:
  • Source: Customer checking account (debit $100)
  • Destination: Merchant account (credit $100)
  • Single source, single destination, equal amounts
A transaction that splits funds between multiple destinations:
  • Source: Customer account (debit $103)
  • Destinations:
    • Merchant account (credit $100)
    • Fee collection account (credit $3)
  • Single source, multiple destinations
Multiple sources funding a single destination:
  • Sources:
    • Primary account (debit $500)
    • Secondary account (debit $300)
  • Destination: Vendor account (credit $800)
  • Multiple sources, single destination
Multiple sources and destinations in a single transaction:
  • Sources:
    • Customer A (debit $200)
    • Customer B (debit $300)
  • Destinations:
    • Vendor account (credit $450)
    • Tax account (credit $50)
  • Multiple sources, multiple destinations

​
Best practices

1

Use descriptive transaction descriptions

Include meaningful descriptions that explain the purpose of each transaction. This helps with auditing and troubleshooting.
2

Verify account balances before transacting

Ensure source accounts have sufficient balance before creating transactions to avoid rejections.
3

Use metadata for integration context

Store external reference IDs, order numbers, or other system identifiers in transaction metadata for traceability.
4

Group related operations logically

When possible, combine related transfers into a single transaction rather than multiple separate transactions.
5

Review transactions before confirming

Double-check source accounts, destination accounts, and amounts before submitting. Transactions cannot be edited after creation.

​
Transaction Routes integration

Transactions can be validated against Transaction Routes before processing. Transaction Routes define rules about which accounts can transact with each other, providing an additional layer of control over your financial operations.