APO / Failure labInteractive portfolio demo

Try to make it pay twice.

Each button authorizes a new, isolated simulated payment. The selected test shows its invoice amount. Introduce a failure, then inspect what actually happened.

Preset invoices$500 / $600 USD

Choose a failure. No experiment has run yet.

Choose an experiment

Expected: Each challenge shows the path it will test. Operation counts are expectations, not results.

What arrivedNo request yet

Pay the vendor $500.00 for the invoice.

APO

Ready for a challenge

What actually happened—

No payment result yet

Actual payment result

Your challenge. The backend's answer.

Money stays unknown until pay-core returns a payment snapshot.

Recorded operations 0

Payment-service calls and local ledger work. History may be incomplete. Select a row for details.

Blue: returned or identifying fields Amber: error or unknown Green: verified identity match

Showing 0 of 0 recorded operations

No recorded operations yet.

    Select a recorded operation

    Choose a row to see what it did and how it ended.

    Current related evidence

    This is the latest payment snapshot and ledger state, not the historical response to this operation.

    Complete recorded operation JSON
    No selection.

    Simulated assistant proposal

    —

    No proposal yet.

    Recorded source

    Policy decision

    —

    One payment, two accounting sides

    Debit and credit balance to net zero because they record opposite accounting sides of one payment. Net zero does not mean nothing was charged. The captured amount is shown separately above.

    No evidence yet
    Account Debit Credit

    Entry identities

    No entries

    Technical test plan and observed counts

    Technical backend state and exact policy verdict

    USD amounts are in cents: 50000 = $500.00. This explains units, not a policy setting.

    No backend state yet.

    Captured amount: pay-core. Recorded entries: ledger. Workflow: Inngest.