Before you begin
- Install the Straddle CLI and configure an API key for the environment you want to analyze.
- Confirm your integration type and acting account.
- Choose the number of days to include. The window ends today, using the local time zone of the computer running the CLI.
- Keep the same context and database throughout. Add the same
--db PATHto eachsyncandcashflowcommand if you use a custom database.
Run the workflow
1
Confirm the account and environment
runtime_context.environment, runtime_context.integration_type, and runtime_context.acting_account. For SaaS or marketplace, select the account if needed and check again:2
Refresh payment records
sync_complete event and a final sync_summary with success: 1, warned: 0, and errored: 0. Review any sync_warning or sync_anomaly before drawing conclusions, including findings that accompany exit code zero.3
Compare daily volume
4
Compare longer periods
date is its first day.Interpret the results
Payments are grouped by
created_at. Full timestamps are converted to the computer’s local time zone; date-only values keep their recorded calendar day. Records with missing or unparseable creation dates are skipped. The calculation puts payment_type: payout in payout volume and treats other values, including unknown types, as charge volume.
A value of 12500 represents $125.00. A negative net means payout creation volume exceeds charge creation volume for that period. Check payment statuses and funding evidence before using the amount to explain an actual bank transfer.