Payment executions

Every payment attempt, what happened to it, and what to do about the ones that failed.

Payment executions in SigmaPointPi
/payment-executions

An execution is the attempt to move money on a rail. It is distinct from the payment record, because one payment can be attempted more than once and each attempt has its own outcome.

This log is where you look when somebody says they did not receive money you believe you sent. It carries the rail, the trace, the timestamps and the response from the institution.

Where everything sits

Moved by month
Moved by month
Moved
Moved
Total
Total
Settled
Settled
In flight
In flight
Failed / returned
Failed / returned

How to work this page

Read the state, not the intent

Submitted, in flight, settled, returned and failed are different. A payment marked paid in the ledger and returned on the rail is the case that hurts.

Use the trace when you call the bank

Every execution carries the reference the institution knows it by. It turns a twenty minute call into a two minute one.

Handle returns deliberately

A returned payment puts the money back and leaves the bill unpaid. It does not retry itself, because a return usually means something needs fixing first.

Read the failure reason

The institution's own reason is shown rather than a generic message, because insufficient funds, a closed account and a blocked payment need different responses.

On a phone

Payment executions on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

Can a settled payment reverse?

ACH can be returned for several days after settlement. A wire generally cannot. The window for each rail is shown on the execution.

Why would a payment be held?

An approval not yet given, a vendor bank change awaiting confirmation, or a freeze. The reason is on the execution.