Status & what happened when things wobbled

Some payments settled normally in Stripe while the ledger occasionally showed the wrong kind of identity story (for example, looking anonymous when it shouldn’t, or feeling inconsistent between member and envelope flows). Your money stayed with Stripe the whole time, this was about clarity and correctness, not missing funds.

• We now tag each checkout with one clear “authority” label end-to-end, so member, envelope, and guest flows can’t blur together.
• Checkout details are stamped consistently before money moves, and follow-up wiring respects those labels.
• Checks now read from a purpose-built view so we never have to bend the ledger’s core rules to ask basic questions.

Our public status page recorded about 17 minutes of downtime on the Supabase connectivity check while other headline services stayed up. Think of it as a canary moment, not necessarily the same as “the app was down for everyone.”

• Systems returned to green on the timeline you see on the status site.
• We matched that story with internal monitoring so we could confirm recovery and watch for echoes.
• When in doubt, status.haylofriend.com is the friendly place to double-check.

A slice of successful checkouts didn’t appear as credits in your ledger because an older automation conflicted with our rule that ledger rows stay factual and never carry improvised story text.

• We removed the conflicting automation and kept the protections that keep your ledger trustworthy.
• We filled in historical rows safely so settled payments line up with what you’d expect to see.
• We verified the gap stayed closed so future payments don’t repeat the same surprise.