The source charged a fee your books never anticipated.

Conclusion

Concluded by ruleset-v2 in run c2f01047, as of 2026-07-02 17:48 UTC.

What matching tried

1. Duplicate sweepSurvived — no other Stripe record shares this id or reference.passed
2. Fee schedule checkNo fee schedule entry anticipates this charge for the period.broke here
3. Exact-reference passNo ledger entry references it.broke here
4. Settlement-lag windowPast its settlement-lag window → break.broke here

The transaction

identity

stripe / acct_mercadia / txn_fee_radar_0001

type

fee

amount

−$8.50

occurred

2026-05-15 03:00 UTC

observed

2026-07-02 17:48 UTC

version

v1 · current

normalized by

stripe-v1

The raw record

{
  "id": "txn_fee_radar_0001",
  "fee": 0,
  "net": -850,
  "type": "stripe_fee",
  "amount": -850,
  "object": "balance_transaction",
  "source": null,
  "status": "available",
  "created": 1778814000,
  "currency": "usd",
  "description": "Radar for Fraud Teams — May",
  "fee_details": [],
  "available_on": 1778976000,
  "reporting_category": "fee"
}

The ingestion batch

source

stripe

idempotency key

stripe:acct_mercadia:222471279ce675758f90bb872bb8bd978c013794250c23777e66777cda700b6c

landed

2026-07-02 17:48 UTC

status

normalized