Letterbook
All docs

Letterbook Docs

Connect Stripe

Give Letterbook billing context for subscriptions, invoices, charges, and refunds.

Last updated June 25, 2026

What this guide covers#

Connect Stripe so Letterbook can resolve billing questions with subscription, invoice, charge, and payment context.

Stripe context helps the AI and support team answer account-specific billing tickets without switching tabs. It is especially useful for refunds, cancellations, failed payments, invoice questions, plan changes, and "why was I charged?" tickets.

Setup steps#

  1. Authorize Stripe from Letterbook.
  2. Choose the Stripe account and mode you want to connect.
  3. Confirm how Stripe customers should match Letterbook conversations, usually by email or customer ID.
  4. Review the subscription, invoice, charge, and payment fields available to support.
  5. Write billing policies in the internal knowledge base.
  6. Decide which actions require human approval.
  7. Test common billing tickets before using the integration in production.

Configuration details#

  • Use the least-privilege access model available for the workflows you need.
  • Separate test-mode validation from live billing operations.
  • Confirm whether the support workflow only reads Stripe data or can stage actions.
  • Require approval for refunds, cancellations, credits, and subscription changes.
  • Disconnect or rotate access when ownership changes.

Common support workflows#

  • Customer asks why they were charged.
  • Customer requests a refund.
  • Customer wants to cancel or downgrade.
  • Customer cannot access paid features after upgrading.
  • Customer needs an invoice or receipt.
  • Customer payment failed and they need to update payment details.

For each workflow, write a policy that tells Letterbook what to check and what action can be suggested.

Approval guidance#

Keep a human in the loop for money-moving or account-changing actions. A good workflow lets the AI gather context, draft the reply, and stage the proposed action, while a teammate confirms the final decision.