stripe.review.resolve
Explicitly classify a Stripe suspense movement with id, treatment, provenance reason, expectedRevision and idempotencyKey. Original financial facts remain preserved.
/api/v1/accounting/stripe.review.resolvePermissions
Who can call it
Retries
MCP
accounting_stripe_classifyFields
idstring (ID)RequiredThe record's ID.
treatmentenumRequiredincomeincome_refundexpenserefundfeetransferreasonstringRequiredA short note saying why, kept in the record's history.
10–2000 characters
expectedRevisionintegerRequiredThe record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.
at most 9007199254740991 · greater than 0
idempotencyKeystringRequiredAny unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.
8–200 characters
Example
curl https://app.getoatmilk.com/api/v1/accounting/stripe.review.resolve \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"treatment": "income",
"reason": "Synthetic example from the docs",
"expectedRevision": 3
}'{
"data": { … }
}Try it
Try it
Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.
curl https://app.getoatmilk.com/api/v1/accounting/stripe.review.resolve \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"treatment": "income",
"reason": "Synthetic example from the docs",
"expectedRevision": 3
}'More in Stripe.