From intent to receipt
A purchase and a payment have different lifecycles. TilcAI aims to connect them while distinguishing authorization, settlement and fulfillment.
Intent
The person requests a product or service. The principal and acting agent are identified.
Verifiable offer
The business confirms price, availability, expiry and payment destination. The model does not invent terms.
Validation and policy
Identity, recipient, limits and offer version are checked. ALLOW is not a signature.
Exact authorization
The owner approves amount, asset, network, recipient and expiry through a trusted signer.
Payment and reconciliation
An idempotent attempt follows an enabled route. A timeout is investigated before retrying.
Receipt and fulfillment
The financial receipt proves settlement. Business confirmation proves booking or delivery.
Shared identifiers
principalId · agentId · businessId · quoteId · orderId · paymentAttemptId.
Paid does not mean delivered. Cancellation, refund and dispute resolution need their own commercial rules.
Availability depends on your instance. Check /health and /v1/routes before integrating.