jinko agent-pay submit

Present a trip ID and a Shared Payment Token: Jinko schedules the agent fulfillment and redeems the token to authorize the booking server-side, advancing it to fulfillment. If the issuer requires 3-D Secure, the response carries payment_status requires_authentication and an authentication_url (no checkout_url): send the traveller to authentication_url + “#hv=” + the token’s next_action.use_stripe_sdk.value, then poll trip-status. Only a declined card returns a checkout_url fallback.

Usage

jinko agent-pay submit [options]

Options

Flag	Required	Description
`--trip-id <id>`	Yes	trip ID (from the trip command)
`--token <spt>`	Yes	Shared Payment Token (spt_…)
`--quote-id <id>`	No	the quote_id checkout returned. With it the payment is bound to that quote: a quote_id that is not one of the trip’s quotes is refused and nothing is charged, an expired one is refused with QUOTE_EXPIRED, and the same trip, quote and token again returns the first attempt’s outcome instead of charging again. Without it the trip’s latest valid quote is charged and the answer names it as quote_id. JSON: quote_id.

Introduction

Travel Demand

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Account & utilities

Usage

Options

​Usage

​Options

Usage

Options