Vision Developers
POST/pay/{token}/checkout

Start Stripe Checkout for the amount still owed: us_bank_account (ACH) or card.

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
startPayPageCheckout
Canonical origin
https://accounting.runonvision.com

Availability: This is a preview contract with runtime status not-public. Publication documents an approved interface; it does not imply public production access.

Purpose and use cases

Start Stripe Checkout for the amount still owed: us_bank_account (ACH) or card.

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/pay/{token}/checkout

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/x-www-form-urlencoded — required for the documented request representation.

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

Path and query parameters

NameLocationTypeRulesDescription
tokenpathstringrequired; pattern ^[A-Za-z0-9_-]{43}$The invoice's pay link token (43 URL-safe characters).

Request body

Media type: application/x-www-form-urlencoded. The body is required.

FieldTypeRulesDescription
methodus_bank_account | cardrequiredNot described in the contract.

Runnable examples

Placeholder values are generated from the approved schema and are not live credentials or customer data. Replace every angle-bracket or shell variable value. Examples cannot be run until the App has a routed base URL and your client has the required grant.

cURL
curl 'https://accounting.runonvision.com/pay/${TOKEN}/checkout' \
  --request POST \
  --header 'accept: application/json' \
  --header 'content-type: application/x-www-form-urlencoded' \
  --data-urlencode 'method=us_bank_account'
JavaScript (server-side)
const response = await fetch('https://accounting.runonvision.com/pay/${TOKEN}/checkout', {
  method: 'POST',
  headers: {
    accept: 'application/json',
    'content-type': 'application/x-www-form-urlencoded',
  },
  body: new URLSearchParams({
  "method": "us_bank_account"
}),
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()
Python 3 standard library
import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://accounting.runonvision.com/pay/${TOKEN}/checkout',
    data=urllib.parse.urlencode({"method":"us_bank_account"}).encode(),
    headers={
    "Accept": "application/json",
    "Content-Type": "application/x-www-form-urlencoded"
},
    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

StatusMeaningSchema
303To Stripe Checkout, or back to the pay pagenot specified
404Unknown or replaced linkstring
502Stripe did not answerstring

Success response schema

No schema is declared.

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.

  • 303 — To Stripe Checkout, or back to the pay page
  • 404 — Unknown or replaced link
  • 502 — Stripe did not answer

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.
  • 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.

Contract history and evidence