Creating a Transaction

Create a new Transaction in the Console using the 1:1 or n:n wizard to move Asset balances between source and destination Accounts by alias.

A Transaction moves value between Accounts in a Ledger. Create one only after the Asset, source account, destination account, and any required Accounting Route are ready.

Before you start

---

Confirm that:

• The source and destination Accounts exist in the selected Ledger.
• Both Accounts use the Asset selected for the Transaction.
• You know each Account alias. A leading @ is a common convention, not a requirement.
• Source accounts allow sending and destination accounts allow receiving.
• If Validate Routes is on, the Transaction must match an existing Accounting Route.

Create the Transaction

---

1. From the Transactions page, click the New Transaction button.

2. The New Transaction modal will open. Select the type of transaction you want to create:

   • Simple 1:1 - Transactions using one source and one destination
   • Complex n:n - Transactions using more than one source or destination
3. After selecting the transaction type, the New Transaction page opens with a step-by-step form:
4. When all the information is correct, click the Go to Review button.

5. The Console shows a review page with a summary of all the transaction information:

   • Transaction value and asset
   • Source and destination accounts
   • Individual debit and credit operations
   • Metadata records (if any)
6. Review the information carefully. If everything is correct:

   • Click Send Transaction to submit and view the transaction details
   • Click Send and Create another to submit and immediately start a new transaction
7. On success, the Console opens the transaction details page with the transaction summary, data, and status.

Field guide

---

Transaction Data

Field	What to enter	Example
Transaction description	Optional business description of the movement.	Customer payment to merchant
Accounting route group	Optional route classification when your setup uses route validation or grouping.	Pix Transfer Group
Transaction Route	Select the Transaction Route associated with the transaction.	Pix Transfer Route
Asset	Asset used by the Transaction. It must match the selected Accounts.	BRL
Value	Total amount to move. For complex transactions, source totals must equal destination totals.	100.00

Source/Destination

Field	What to enter	Example
Source	Account alias that will be debited.	@customer_123
Destination	Account alias that will be credited.	@merchant_456

Operations

Field	What to enter	Example
Operation description	Optional description for the operation.	Debit for the source account
Chart of accounts	Optional name of the Chart-of-Accounts that the operation belongs to.	Pix debit - source
Operation Route	Optional operation route for this transaction leg.	Checking account validation for Pix
Metadata Key	Optional classification or integration field name.	externalReference
Metadata Value	Value for the metadata key.	order_98765

Transaction types explained

---

Simple Transaction (1:1)

Use for straightforward transfers between two accounts:

• One source account (debit)
• One destination account (credit)
• Same amount debited and credited

Example: Transfer $100 from Customer A to Merchant B.

Complex Transaction (n:n)

Use for transactions involving multiple parties:

• Multiple source accounts (debits) and/or multiple destination accounts (credits)
• You can distribute amounts across accounts
• Total debits must equal total credits

Examples:

• Payment with fees:
  • Customer pays $103
  • Merchant receives $100
  • Fee account receives $3
• Consolidated payment: Multiple customers fund a single vendor payment

The fields in the Metadata tab are open. There are no default keys or values. Use consistent key names across your Organization, such as externalReference, orderId, or channel, to link Transactions back to source systems for reconciliation and audit.

What to do next

---

After sending the Transaction, review the details page and confirm the status, source operation, destination operation, and account balances.

Create a Transaction using JSON

Create a Transaction programmatically with the JSON endpoint.

Retrieve a Transaction

Inspect the Transaction status and operations via API.