Stripe

Use Stripe when an agent needs to help a verified customer with billing information. The action card requires a Stripe connection; if it is not connected, go to Integrations and finish the connection first. When more than one connection is available, choose the intended one. Configure only the capabilities the agent needs: invoices, subscriptions, payment methods, and billing-address updates.

The runtime requires a verified customer identity supplied by your embedding site through a signed JWT that identifies the customer’s Stripe record. Without that identity, the action cannot retrieve customer billing data. It can retrieve the configured billing information and can update a billing address when that capability is enabled. It does not document support for charging, refunds, cancelling subscriptions, changing payment methods, or exposing full card data.

Stripe is high risk. In widget chat with action approval enabled, the visitor must confirm each Stripe action before it proceeds. Test with a non-production customer record, confirm the identity integration is present, and review the action log after use. Avoid asking visitors to paste sensitive payment data into the conversation.