Stripe Connect webhook. Signature-checked and deduplicated; a succeeded payment is recorded against its invoice (or kept as customer credit when the invoice is no longer payable), and a Stripe refund is recorded once against its payment.

The approved contract does not provide a longer purpose statement for this operation.

App

Accounting

Contract

Accounting API 0.32.0

Lifecycle

preview

Runtime

not-public

Operation ID

receiveStripeConnectEvent

Canonical origin

https://accounting.runonvision.com

Purpose and use cases

Stripe Connect webhook. Signature-checked and deduplicated; a succeeded payment is recorded against its invoice (or kept as customer credit when the invoice is no longer payable), and a Stripe refund is recorded once against its payment.

The owning App is Vision Accounting. Accounting owns financial records, exact arithmetic, approvals, audit evidence, workspace grants, and ledger invariants.

Business use cases and out-of-scope behavior are not yet declared in the approved OpenAPI description.

Request

POST https://accounting.runonvision.com/stripe/webhook

Authentication and authorization

No authentication requirement is declared for this operation.

Headers

• Accept: application/json — recommended where a JSON response is declared.
• Content-Type: application/json — required for the documented request representation.

Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.

Path and query parameters

Request body

Media type: application/json. The body is required.

Runnable examples

curl 'https://accounting.runonvision.com/stripe/webhook' \
  --request POST \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{}'

const response = await fetch('https://accounting.runonvision.com/stripe/webhook', {
  method: 'POST',
  headers: {
    accept: 'application/json',
    'content-type': 'application/json',
  },
  body: JSON.stringify({}),
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()

import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://accounting.runonvision.com/stripe/webhook',
    data=json.dumps({}).encode(),
    headers={
    "Accept": "application/json",
    "Content-Type": "application/json"
},
    method='POST',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.

Responses

Success response schema

Errors and troubleshooting

Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.

• 400 — Signature rejected or malformed event
• 404 — Stripe Connect is not set up on this Vision
• 500 — Processing failed; Stripe retries

Collection behavior

Pagination: not declared. Filtering/search: not declared. Sorting: not declared.

Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.

Operational behavior

• Rate limit: No operation-specific limit or 429 response is declared.
• Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
• Idempotency: No idempotency header or replay window is declared.
• Concurrency: No ETag, If-Match, or optimistic-version header is declared.

Security and privacy

• Keep client credentials and bearer tokens on trusted servers.
• Send only to the exact approved HTTPS origin and audience.
• Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
• Do not log credentials, tokens, complete private payloads, or secrets.

Edge cases and known documentation gaps

• No detailed operation description.
• One or more parameters have no field-level description.
• The request body has no purpose or conditional-rule description.
• No machine-readable success schema.
• Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Related operations and workflows

No related operation is identified by the contract tags.

Contract history and evidence

• Contract version: 0.32.0
• Approved snapshot SHA-256: 4dd988e12dc08be93bc7f1ebb4d725c40646c46f3d63a380a48a439077d53eea
• Approval: Anthony, 2026-11-03T01:23:28.091Z (anthony-docs-live-20261102)
• Download the authoritative OpenAPI 3.1 snapshot