Catalog authority
Product, amount, currency, release hash, and merchant live on the server. The browser selects an ID, never a price.
Payment orchestration for the Mobleysoft estate
Payments are not the product. Completion is.
VendyAI connects a fixed product catalog to hosted payment collection, signed events, entitlements, and hash-verified delivery. One flow for every venture, without trusting prices or success claims from the browser.
VDY / TRANSACTION RAILNO CARD DATA HERE
- 01Catalog intentServer-owned price
- 02Provider checkoutStripe-hosted today
- 03Signed eventHMAC verified
- 04EntitlementIdempotent ledger
- 05DeliverySHA-256 verified
One rail, many ventures
A payment layer that knows what happens after approval.
Provider routing
Stripe is the first external rail, isolated behind one adapter so VendyAI can later route by geography, cost, risk, and settlement need.
Entitlement ledger
Signed webhooks are processed once. Paid sessions become expiring, bounded download rights rather than optimistic redirect pages.
Verified fulfillment
A payment cannot begin unless the release exists, matches its catalog digest, and passes the configured distribution gate.
Estate primitives
Checkout creation, receipts, refunds, subscriptions, metering, tax, and venture revenue splits converge behind one reusable interface.
Provider independence
VendyAI preserves the customer and product contract while providers become replaceable settlement infrastructure.
The narrow waist
A single request begins a controlled flow.
VendyAI accepts a catalog product ID. It refuses arbitrary amounts, refuses unsigned provider events, and refuses delivery when release integrity fails.
- No raw card fields
- No placeholder secrets
- No unauthenticated success endpoint
- No public release path before entitlement
POST /api/v1/checkout/create
{
"product_id": "unlost-launch"
}
201
{
"status": "created",
"checkout_url": "https://checkout.stripe.com/..."
}