Confirm a booking after payment settles, by payment reference (public)
Effect
ask
Awaits an outcome — the call returns the response below.
Caller
public
The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost
free
What one call costs, so you can budget before acting.
Reversible
yes
The effect can be undone by a later call.
Idempotent
yes
Safe to retry as-is.
Send it with your agent
One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.
The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.
Request
Validated before dispatch — an invalid payload is refused with the fix, never half-applied.
paymentRefstring required
Response
What comes back from the call.
okboolean
errorstring
Traffic
Every call to booking:confirm-payment, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.
Counting…
Wiring
Every place in the open source that names booking:confirm-payment, and the file that
answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no
import edge to follow and a grep is the honest shape of the question.
Structure, not volume — the count is in Traffic above.
Called from
API route2
one.ie/web/src/lib/receiver-index.generated.ts:62
one.ie/web/src/lib/resolvers/booking.ts:665
Workflow1
one.ie/web/src/lib/workflow-templates.ts:1987
→
Answered by
booking:confirm-payment one.ie/web/src/lib/resolvers/booking.ts:441
Dispatched through POST /api/ask/booking:confirm-payment, after the envelope
validates the payload.