Payment Link Flow

Automating Stripe payment links for booking deposits is handled by triggering the send_payment_link capability during booking workflows, which instantly generates and sends a Stripe Checkout link scoped to a specific booking_id. It requires Stripe access to function.

Scoping a Stripe Checkout link to a specific booking artifact ensures traceability and avoids duplicate links in the same turn. The process enforces referencing artifacts like booking_id or gift_card_id to contextualize the payment link securely.

Collecting balances or gift payments using Stripe Checkout links is achieved by integrating the send_payment_link capability into your workflow. It generates targeted payment links scoped to artifacts like gift_card_id, ensuring accurate payment collection for various transaction types.

A booking_id or similar artifact reference is required to generate a contextualized Stripe payment link. Enforcing artifact referencing ensures the payment link is properly scoped to the specific transaction, preventing duplicate links and maintaining payment traceability.

Duplicate Stripe payment links in the same turn occur when artifact scoping is not properly enforced. The workflow avoids duplicate links by requiring references to specific artifacts like booking_id or gift_card_id, ensuring only one link is generated per payment trigger.