| Line | Unit | Value |
|---|---|---|
| 1Synthetic fee line | not priced | — |
| 2Synthetic fee line | not priced | — |
| 3Synthetic fee line | not priced | — |
| 4Synthetic fee line | not priced | — |
| 5Synthetic fee line | not priced | — |
| 6Synthetic fee line | not priced | — |
Run your own operation. See every decision behind it.
insimbi is a proposed payments-control surface for merchants. The idea: you set the rules, you see the evidence for every decision, and you reconcile every row back to its source ticket — on your terms.
A mechanism to examine. Not a live payment service. Every record below is a synthetic fixture.
Decisions you can trace
Each ticket line points back to the decision that produced it. Rule and cost references remain placeholders pending owner and counsel review.
See the ticket conceptSearch, export, reconcile
Search, export and reporting concepts run in your browser against synthetic records and send no request.
See the control conceptsMandates you approve
Proposed agent tooling checks a mandate before any simulated action. No credentials, endpoints or clients exist.
Run the agent simulationThe full prototype · 11 frames
Trace the decision. Read the ticket.
Proposed design: a control plane would record decisions and expose their evidence alongside a ledger. This local prototype connects to no live service.
The ticket concept ties each line and later event to a source decision. Rule and cost references remain placeholders pending owner and counsel review.
A mechanism to examine. Not a live payment service.
Review the onboarding gates · Inspect the reporting example
Explore predictive scenarios · Run an agentic payment simulation
Validate the onboarding problem and its evidence.
Review the open product, architecture, privacy, and commercial decisions before enabling customer intake or connecting to a provider.
Ticket concept · synthetic fixture
This screen illustrates a proposed record shape only. It contains no real card, payment, pricing, regulatory decision, or settlement data. References are placeholders, not verified sources.
| Line | Basis | Unit | Value |
|---|---|---|---|
| 1Synthetic fee line | Illustrative only; source unverified | not priced | — |
| 2Synthetic fee line | Illustrative only; source unverified | not priced | — |
| 3Synthetic fee line | Illustrative only; source unverified | not priced | — |
| 4Synthetic fee line | Illustrative only; source unverified | not priced | — |
| 5Synthetic fee line | Illustrative only; source unverified | not priced | — |
| 6Synthetic fee line | Illustrative only; source unverified | not priced | — |
- FIXTURE-01Decision · placeholder outcome; no rule evaluated
- FIXTURE-02Evidence · source reference pending verification
- FIXTURE-03Owner · not assigned
- FIXTURE-04Event · illustrative only; no settlement initiated
- FIXTURE-05Decision link · schema concept; no liability conclusion
Event, state, and timing are not simulated.
Search, export, and cutoff concepts
Controls run against fixed local fixtures. They do not validate provider limits, interpret settlement timing, or alter any real schedule, account, or payment.
Search concept
Local-only synthetic records. Search runs in this browser and sends no request.
5 synthetic records match
| Fixture | Type | State |
|---|---|---|
| SYN-001 | Review | Working |
| SYN-002 | Intake | Fired |
| SYN-003 | Exception | Working |
| SYN-004 | Report | Plated |
| SYN-005 | Agent call | Void |
No synthetic records match that search.
Fixture count only. No provider data or capacity is measured.
Export workflow concept
- period
- not selected
- rows
- not generated
- format
- CSV · synthetic fixtures
- manifest
- not generated
- cutoff
- not configured
The browser creates a file from the fixtures above. No data is uploaded.
Cutoff concept
Preview only. The chosen values are not validated against any provider or schedule.
- cutoff
- timezone
- effective date
- approval
- Not available
No preview calculated. No schedule or settlement is changed.
Developer contract · proposal
The local OpenAPI file is an illustrative contract draft, not a deployed endpoint. SDK, CLI, MCP, discovery, authentication, and authorization details are proposals and have not been implemented or approved.
Illustrative contract file
This path identifies a local draft only; no public API host or generated client is available.
Generation and fingerprints have not been verified.
No credentials or token endpoint
Authentication, authorization scopes, token lifetime, and agent access remain design decisions. This prototype issues no credentials and makes no authenticated requests.
No client is registered
Client lifecycle, grants, rate limits, and secret rotation require security and owner decisions. No identity, secret, or access token exists in this scaffold.
Proposed tool shapes
-
search_transactionsproposed
- in
- query: string · cursor?: string · limit: pending decision
- out
- synthetic rows · cursor design pending
-
export_settlementproposed
- in
- period: { from: date, to: date } · format: "csv" | "parquet" · cutoff?: "HH:MM"
- out
- job_id: string · status: Fired | Working | Plated | Void · manifest?: { rows: int, sha256: string }
-
get_ticketproposed
- in
- id: string
- out
- Ticket { header, lines: Line[6], decisions: Decision[], events: Event[], status }
-
preview_cutoffproposed
- in
- time: "HH:MM" · tz: iana · applies_from?: date
- out
- effective_from: datetime · next_cutoff: datetime · warnings: Warning[]
No public discovery endpoints
Documentation and machine-discovery paths are candidate design elements only. This prototype serves none of them; interoperability and ownership remain open.
Preview only · no configuration write
{ "preview": true,
"applied": false,
"cutoff": null,
"reason": "No live service is connected" }
No settlement, account, or provider configuration can be changed from this scaffold.
Pricing and billing are undecided
No rates, fee totals, credit balances, or billing events are represented. Prepaid credits, post-billing, flat fees, and usage-based models remain options for product and finance owners to evaluate.
| Category | Basis | Rate | Amount |
|---|---|---|---|
| Processing | not defined | — | — |
| Optional services | not defined | — | — |
| Platform | not defined | — | — |
Billing model
Candidate approaches include prepaid credits, post-billing, a flat fee, or another owner-approved model. No option is selected and no price is published.
Commercial and finance owners: select the commercial model and define its source of truth, customer disclosures, and approval process before publishing rates.
This page is a design placeholder, not a quotation or offer.
Design-partner intake is not enabled
No personal or business information is collected in this prototype. A future intake flow requires approved ownership, privacy notice, consent, retention, and response procedures.
There is no form submission, ticket creation, mailing list, or owner notification connected here.
Operator queue concept
Local synthetic fixtures illustrate a possible review queue. No real account, merchant, dispute, user, or operational state is represented. Row selection only updates this page.
| Status · age | Ticket | Type | Detail | Owner | Select |
|---|---|---|---|---|---|
| Workingfixture | SYN-001 | Review | Illustrative document check | unassigned | |
| Firedfixture | SYN-002 | Intake | Illustrative onboarding step | unassigned | |
| Platedfixture | SYN-003 | Review | Illustrative completion state | unassigned |
3 synthetic fixtures
Selecting a row changes only the local preview.
Review the business, customer, agent, then mandate.
This acquisition walkthrough uses a synthetic merchant fixture. It collects no identity data, documents, contact details, or eligibility decisions.
Bind an agent to one principal and one scope.
Fixture mandate MND-DEMO-001 names no real person or business. It demonstrates a principal, delegated agent, allowed action, payee, amount cap, expiry, confirmation step, and revocation path.
| Field | Synthetic value | Control |
|---|---|---|
| Principal | DEMO-TENANT-01 | Merchant-controlled |
| Agent | AGENT-FIXTURE-01 | Version-bound identity · proposed |
| Action | Preview one payment request | Human confirmation required |
| Payee and cap | PAYEE-FIXTURE-01 · USD 25.00 (synthetic) | One request · local fixture only |
| Expiry / revoke | 15-minute scenario window | Merchant admin revokes; real mechanism undecided |
No mandate is issued. Preview only.
Review the inert design-partner intake boundary · Inspect the proposed agent contract
Reconcile every row to its source ticket.
Every count below is a synthetic fixture. No business activity, fee, settlement, route, or performance is measured; report rows exist only in this browser session.
Reconciliation sample
Each illustrative row points to a synthetic ticket or event. The table is not a settlement ledger.
| Record | Source ticket | State | Evidence | Synthetic amount |
|---|---|---|---|---|
| SYN-001 | FIXTURE-01 | Illustrative | Decision reference pending | — |
| SYN-002 | FIXTURE-01 | Illustrative | Event link not modeled | — |
| SYN-003 | FIXTURE-01 | Illustrative | Manifest not generated | — |
- schema
- not assigned
- checksum
- not generated
- retention
- not decided
Open the synthetic ticket · Review export-job and cutoff concepts
Preview the next window. Keep the decision visible.
This is not a trained model or a forecast. Choose a fixed synthetic scenario to inspect how a future operator could compare expected payment demand and exceptions before taking action.
Select a synthetic operating day
All values are fabricated test data. No payment history or external model is queried.
Baseline fixture
- signal
- Fixture baseline · no model learned
- suggested review
- Inspect demand window before scheduling
- authority
- Human/operator · no automatic action
Not a prediction, recommendation, capacity estimate, or payment decision.
| Fixture | Expected intents | Review cases | Range |
|---|---|---|---|
| Baseline | 120 | 9 | ±20 |
| Demand surge | 180 | 14 | ±35 |
| Exception cluster | 96 | 22 | ±28 |
Preview the request. Check the mandate. Simulate the result.
The agent is a delegated actor, not the principal. A local rule checks this fixture against a synthetic mandate; it does not contact a merchant, bank, network, wallet, or payment service.
Payment intent
- principal
- DEMO-TENANT-01
- agent
- AGENT-FIXTURE-01 · version 0.1
- payee
- PAYEE-FIXTURE-01
- mandate
- MND-DEMO-001 · USD 25.00 max (synthetic)
No request previewed
- mandate check
- not run
- decision
- not simulated
- side effect
- none · no funds move
A within-limit request can produce only a simulated authorization result. An over-limit request is denied by the fixture rule.
Review the KYA and mandate gates · Inspect synthetic reporting