Open a booking hold
booking_intentWHAT BECOMES OF THE MONEY: it sits in an on-chain escrow that stays the buyer's. On a booking the wallet that funds the deposit is the wallet that confirms it — one signature on the booking page, no code needed — and the shop's no-show terms, which the buyer accepted before paying, can pay the deposit to the shop after the appointment. A goods hold's window is 70 minutes by default — a 60-minute reap window plus ten minutes of grace; an appointment deposit's window comes from the shop's own terms. A hold nobody acts on stays locked when its window closes; each checkout hold also carries a pre-signed return that pays only the wallet the hold was opened for, and sending it automatically at expiry, and handing it to the buyer, is being built. The platform's 2% escrow fee sits inside the same on-chain transaction that completes the order; an unwind back to the buyer carries none. IF THE APPOINTMENT IS CANCELLED, the shop's own cancellation terms decide, and they were SEALED onto this hold when it opened: the free-cancel window, what a late cancel or a no-show keeps, and a dispute window (72 hours on the standard terms). The arbiter enforces the copy recorded at open, not a later opinion. Read the shop's OWN terms back to your human rather than describing a default — ask the shop, never assume. Open a reversible DEPOSIT hold on a real appointment, in your human's name. Same ceiling as checkout_intent and the same reason: this is a HOLD, not a booking that has taken money. A booking's backup code goes to the buyer's own inbox, never to you, and on a checkout the code that completes the order lands there too; an unfunded hold hands the slot back on its own. FUND IT YOURSELF when buyer_wallet is your own purse — the human should be confirming a deposit that is already sitting in escrow, not sending one. Hand the funding transaction over only when the wallet is theirs. You must pass the buyer's real email and Stellar public key, and the shop's cancellation policy is consented to by asking for this.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"shop": "<shop>",
"service": "<service>",
"starts_at": "<starts_at>",
"buyer_name": "<buyer_name>",
"buyer_email": "<buyer_email>",
"buyer_wallet": "<buyer_wallet>"
},
"name": "booking_intent"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | anything the shop should know | |
| shop | Yes | the shop's slug | |
| because | No | the brief-line that drove this booking — it rides the buyer's mail | |
| service | Yes | the service id from booking_offer | |
| starts_at | Yes | the opening you want, ISO — from booking_offer's list | |
| buyer_name | Yes | who the appointment is for | |
| buyer_email | Yes | the buyer's real inbox — a booking's backup code goes there, and on a checkout the code that completes the order does too | |
| buyer_wallet | Yes | the wallet this deposit REFUNDS to (G + 55 base32) — your own purse when you hold one, and then you fund it yourself; otherwise the buyer's own key |