FINANCE

Dispute Outcome Archiver and Win-Rate Ledger

When a Stripe dispute closes, archives the full evidence packet to a dated Dropbox folder, records the won/lost outcome and amount in a Postgres ledger.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe dispute closed webhookStripeStripe
  • ActionArchive packet to dated Dropbox folderDropboxDropbox
  • ActionInsert outcome row in Postgres ledgerPostgreSQLPostgres
  • LogicBranch on won vs lost
  • OutputPost outcome note to FrontFront

What it does

Closes the loop after a dispute resolves. It captures the final outcome from Stripe, moves the complete evidence packet into a permanent dated archive in Dropbox, and writes a ledger row so you can track win rate, recovered revenue, and which reason codes you lose most.

When to use it

Use it when you need an audit trail of every chargeback and the analytics to improve your defense over time. Pairs naturally with any of the evidence-assembly workflows as the record-keeping stage.

How it works

  1. 1A Stripe `charge.dispute.closed` webhook fires with the final status and amount.
  2. 2The flow gathers the dispute's submitted packet and moves it to a `disputes/closed/<month>` folder in Dropbox for retention.
  3. 3A Postgres step inserts a ledger row: dispute ID, reason code, outcome, amount, and resolution date.
  4. 4A logic branch separates wins from losses for tailored messaging.
  5. 5A Front note posts the outcome to the billing inbox with the running win-rate context.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect FrontShared inbox, conversations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.