Merchants
Bring a purchase or booking journey: the account, quote, cancellation terms, and when the order becomes final.
Explore togetherWhat if payment succeeds but the booking doesn't?
An invitation to build together
Let's give agentic commerce a human side.
Merchants, agent builders, identity and payment providers: bring your experience to OAV and Kiralis integrations.
Something better, together.
A shared language, open to your approach. OAV is independent of any one account backend, assistant, or messaging provider. Bring your own approach to a shared workflow.
There's a place for
what you know.
Bring a real journey, a useful mechanism, or a difficult question. Concrete examples help us build something that works across systems.
Agent builders
Show how your agent establishes intent and resumes the same request after consent, while respecting refusal, expiry, and duplicates.
Explore togetherHow does an interrupted request continue safely?
Identity & payment providers
Bring supported mechanisms, versions, and verifiable evidence. For Kiralis, include eligible pull collection, revocation, and settlement confirmation.
Explore togetherWhat can another system verify about the result?
Experience designers
Help people understand the account, amount, and effect of a decision. Explore changed quotes, stale messages, and one-off versus standing permission.
Explore togetherDoes the person know exactly what they're allowing?
Start small.
Make it work together.
One complete example is a great beginning. Use fictional accounts and amounts, and include a failure case alongside the intended outcome.
- 1 · Bring an example
Describe the interaction.
Identify the human, agent, merchant, quote, and expiry. Show what existing permission covers and what needs a new decision.
- 2 · Review the boundaries
Agree on the evidence.
Define who verifies what, and how refusal, retries, or revoked permission affect the same operation. Record unresolved choices.
- 3 · Test independently
Compare real behavior.
Test agreed versions with another implementation, including successes and failures. Matching status codes alone don't prove compatibility.
Bring your expertise to the table.
A merchant journey, an identity mechanism, a payment flow, or a clear consent experience: start with one example we can test together.