Book a walkthrough
Use casesDevelopersPricingSecurityDocsBlogBook a walkthrough
For developersFewer pings, more shipping

Stop being the answer to why does it do that?

Explain a flow to om once. Support, product and leadership ask om from then on, and you get your focus back.

Book a walkthroughRead the docs
Ishaan’s DMsPayments engineer · Tuesday
7
  • SK

    seller says payout stuck in ON_HOLD since yesterday, why??

    Sana · Support · 10:04
    waiting
    omCash-on-delivery order. Payouts wait 24 hours after delivery (Priya’s fraud rule). It releases at 14:20.
  • RM

    is the refunds fix live for the board demo?

    Rohan · Executive · 10:12
    waiting
    omMerged, not deployed yet. It goes out in Thursday’s release.
  • MD

    can we pay sellers on delivery if we drop that hold?

    Meera · Product · 10:31
    waiting
    omNot without Priya. The hold stops about 40 fraud payouts a month. I’ve asked her.
  • KR

    can I delete payouts/legacy_hold.ts? looks dead

    Karan · New joiner · 10:58
    waiting
    omNo. The settlement job still imports it. Owner: Priya S.
  • FN

    who decided the ₹50k manual review limit? audit is asking

    Farhan · Finance · 11:20
    waiting
    omHead of Risk, June 2026, after refund fraud on new accounts. I sent you the approval record.
  • NS

    is a 2% payout retry failure expected?

    Neha · QA · 11:41
    waiting
    omYes. Gateway timeouts retry once, so 2% is normal. Above 5%, page Payments.
  • TK

    customer refunded twice for one order, what do I check?

    Tara · Support · 12:05
    waiting
    omUsually a gateway retry. Compare the idempotency keys on both refunds first (from Priya’s note).
7 interruptions before lunch.

Ten minutes to teach om a flow.

No docs to write. om maps the flow itself and asks you only what the code can’t tell it.

Connect a repository

Read-only. Your code stays where you run it.

om traces the flow

From the screen to the database, every rule on the way.

/checkout → POST /orders → settle() → COD hold 24h → db.payouts

You add what only you know

om asks a few short questions. Your answers are what it tells everyone else.

om asked Priya S. · Payments lead

Cash-on-delivery payouts wait 24 hours before release. Why 24 hours, and does it apply to every seller?

Answer however suits you.

Fraud on COD orders shows up within a day of delivery (INC-118). It applies to every seller for now. Priya wants sellers older than six months exempt.
What om saved
  • COD payouts wait 24 hours after delivery. Reason: fraud is flagged within a day (INC-118).
Priya approves it before anyone sees it

It reads what you already have.

Code, tickets, docs and threads, connected in minutes. Nobody writes docs for om.

omone memory of how
your company works
GitHubCode and PRs
GitLabCode and MRs
BitbucketCode and PRs
JiraTickets
LinearIssues
ConfluenceDocs
NotionDocs
Google DocsDocs
SlackThreads
ZendeskSupport tickets
PostgreSQLSchemas
TeamsThreads
PDFs and callsBusiness context
In your AI coding tools

Your assistant checks with om before it deletes a rule.

om connects to Cursor, Claude Code and other assistants over MCP, so the reason behind a line arrives with the line.

assistant → om.why("payouts/legacy_hold.ts")
Still used: the settlement job imports it.
Holds COD payouts for 24 hours after delivery.
Reason: fraud is flagged within a day (INC-118).
Owner: Priya S. · approved Jun 2026
assistant → Keeping the file. Asking Priya first.
On every pull request

A PR that changes an approved rule gets a second opinion.

om spots it, explains what the rule protects, and asks its owner before merge.

om on PR #2304 · “Pay sellers on delivery”This removes the 24-hour COD payout hold Priya S. approved in June 2026. It stops about 40 fraud payouts a month. I’ve asked her to review.

Get your afternoons back.

Connect one repository. Teach om one flow. Watch the pings stop.

Book a walkthroughRead the docs