Skip to main content
Use the transactions command to list transfers, inspect a single post, create transactions interactively, and commit, void, or refund inflight work. Reach for this command when you are debugging money movement or testing a flow on Core.
CommandAliasDescription
listlBrowse transfers with filters; add --id for one transaction
createcPost a transfer via interactive prompts
updateuCommit, void, or refund an existing transaction

list

Monitor money movement in a paginated table with amount, currency, status, and related IDs. Filter by --status, --currency, or --balance-id to audit queued work, applied posts, or activity on one account.
Options
OptionTypeDefaultDescription
--{field}string-Filter by any indexed field (for example --status APPLIED, --currency "USD,EUR").
-p, --pageinteger1Page number.
--per-pageinteger10Results per page.
-h, --helpboolean-Show help for this command.
Usage
1

List all transactions

Run the command to view a paginated table of transactions:
Filter and paginate:
200 Success
Status values may appear colorized in your terminal.

list --id

Inspect one transaction end to end: source, destination, reference, status, and metadata. Pass --json when you need precision, inflight flags, or parent/child links exactly as Core returns them.
Options
OptionTypeRequiredDescription
--idstringYesTransaction ID to fetch (for example txn_fa19841f-faa5-4838-9295-b7278a4ff71d).
--jsonbooleanNoPrint the full API object as JSON instead of a formatted summary.
-h, --helpbooleanNoShow help for this command.
Usage
1

Get one transaction

Run the command with a transaction ID:

create

Post a transfer between balances (or indicators) through prompts for amount, precision, parties, reference, and inflight options. Handy for quick manual tests; multi-leg or high-volume flows should go through your application integration instead.
The interactive flow covers common fields. For complex multi-leg or bulk transactions, use your application integration against Core directly.
Arguments The CLI prompts for these values. They are not passed on the command line.
ArgumentTypeRequiredDescription
amountstringYesTransaction amount. Prompt: amount >
precisionintegerYesAmount precision (for example 100 for cents). Prompt: precision >
currencystringYesCurrency code. Prompt: currency >
sourcestringYesSource balance ID or indicator. Prompt: source >
destinationstringYesDestination balance ID or indicator. Prompt: destination >
referencestringYesUnique reference for the transaction. Prompt: reference >
descriptionstringYesShort description. Prompt: description >
allow_overdraftbooleanNoWhether overdraft is allowed. Prompt: allow overdraft >
inflightbooleanNoWhether the transaction is inflight. Prompt: inflight >
meta_dataobjectNoOptional metadata as JSON. Prompt: metadata (json) >. Press Enter to skip.
Options
OptionTypeDescription
--jsonbooleanAfter a successful create, print the full API response as JSON.
-h, --helpbooleanShow help for this command.
Usage
1

Create new transaction

Run the command:
The CLI prompts for each argument:
Press Enter at the metadata prompt to leave it empty.
2

Transaction created


update

Move an existing transaction through its lifecycle: commit inflight funds, void before settlement, or refund after apply. Supply the transaction ID and exactly one of --commit, --void, or --refund.
Arguments
ArgumentTypeRequiredDescription
transaction-idstringYesTransaction ID to update (for example txn_abc123).
Options
OptionTypeDescription
--commitbooleanFully commit an inflight transaction.
--voidbooleanVoid an inflight transaction.
--refundbooleanRefund a transaction.
-h, --helpbooleanShow help for this command.
Usage
1

Commit a transaction

Run the command with --commit and an inflight transaction ID:
200 Success
2

Void a transaction

Run the command with --void and an inflight transaction ID:
200 Success
3

Refund a transaction

Run the command with --refund and an applied transaction ID:
200 Success