Redeem a Shared Payment Token to authorize the booking server-side
Pay for a trip programmatically with a Shared Payment Token, no checkout page. After checkout returns the trip’s agent_spt_params and the agent has minted a token scoped to them, call this to schedule the agent fulfillment and authorize the charge server-side in one step.
Tool description (what the LLM sees)
Submit a Shared Payment Token (SPT) to schedule the agent fulfillment and authorize the booking server-side in one call. This is the agent-pay alternative to sending the user to a checkout page.PREREQUISITE: call checkout first to get agent_spt_params, then mint an SPT scoped to those params.USAGE: submit_agent_payment({ trip_id, shared_payment_token })On success the booking proceeds to fulfillment ({ status, payment_verified: true }). If the issuer requires customer action (3DS) or declines, the response carries a checkout_url, open it in a browser to complete payment manually.
Trip ID from the trip tool, the same trip you called checkout on.
shared_payment_token
string
Yes
The Shared Payment Token (spt_…) minted by the agent platform, scoped to the agent_spt_params returned by checkout.
user_intent
string
No
The end user’s current request in their own words, e.g. “find a cheap flight to Tokyo in mid-June”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional and never changes the result of the call; Jinko uses it to understand demand and improve results.