Developer concepts
A precise contract between intent and status.
This page sketches how an instruction, policy decision, future adapter, and reconciliation event could remain distinct. It is not live API documentation.
Concept only · No production API, endpoint, key, SDK, sandbox, or integration is available.
Conceptual adapter interface
Interface sketch
interface ConceptualAdapter {
// Check whether the synthetic statement has enough information for review.
verify(statement: SyntheticStatement): Verification;
// Represent a future attempt to send an approved mandate.
submit(mandate: ApprovedMandate): SubmissionState;
// Ask a future source for the strongest state it can confirm.
reconcile(reference: SyntheticReference): ReconciliationState;
}Events worth distinguishing
mandate.approved- The user approved the exact reviewed scope.
execution.submitted- A future adapter attempted submission.
execution.accepted- A future rail accepted the submission; this would not mean settlement or biller credit.
execution.settled- A future rail reported settlement; this would not by itself mean biller credit.
item.credited- A future reconciliation source confirmed that the item was credited.
mandate.expired- The proposal passed its deadline before submission.
mandate.cancelled- The user cancelled before submission.
What remains TBD
Schemas, authentication, authorization, providers, error contracts, retries, reconciliation sources, observability, security review, and operating ownership.
Share developer feedback