Payment status
Illustrative confirmation is not reconciliation or invoice issuance.
Request schema from OpenAPI
GET has no request body; Swagger documents paths/context.
Read the operation and next actions
Errors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsReliability, concurrency and recovery
Retry design follows the side effect rather than repeating every request blindly.
Read detailsAPI Explorer — local simulator
Explore requests/responses and failure scenarios using synthetic data; no backend connection.
Read detailsContract boundary
Illustrative confirmation is not reconciliation or invoice issuance.
Exceptions and reconciliation
After timeout, query state rather than create another transaction/command with an unknown prior outcome. Retain correlation/version/evidence without records or credentials in logs.
HTTP example — proposed contract
Request
GET https://records.example.invalid/v1/payment-requests/{paymentRequestId} HTTP/1.1
Authorization: Bearer <example-token>
X-Tenant-Id: synthetic-tenant-001
X-Project-Id: synthetic-project-001
X-Correlation-Id: synthetic-correlation-001Response · 200
{
"paymentRequestId": "synthetic-payment-001",
"state": "CONFIRMED",
"providerRef": "synthetic-provider-001",
"reconciled": false
}Required fields and shared controls
| Item | Proposed rule |
|---|---|
| scope | billing:read |
| required | No request body |
| tenant / project | Token and context must match; headers alone are insufficient. |
| idempotency | POST/PATCH: same key/body returns original result; changed body returns 409; confirm retention window. |
| error | code, message, requestId, correlationId, retryable, details; no sensitive data. |
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment