Stripe

Use Stripe when an agent needs to help a verified customer with billing information. The action card needs a Stripe connection. If no connection exists, go to Integrations and finish the connection there. When more than one connection is available, choose the correct one. Configure only the capabilities the agent needs: invoices, subscriptions, payment methods, and billing-address updates.

The runtime needs a verified customer identity. Your embedding site supplies this identity through a signed JWT that identifies the customer’s Stripe record. Without this identity, the action cannot retrieve customer billing data. The action can retrieve the configured billing information. When you enable the capability, the action can also update a billing address. The action does not support charging, refunds, cancelling subscriptions, changing payment methods, or showing full card data.

The Stripe action is high-risk. If widget chat has action approval enabled, the visitor must confirm each Stripe action before it proceeds. Test with a non-production customer record. Make sure that the identity integration is present. Review the action log after use. Do not ask visitors to enter sensitive payment data in the conversation.