Not by default. Most Stripe-on-WordPress plugins already sync customer, subscription, and invoice data into postmeta or a custom table; SleekAI reads that. For details that are not synced, you can write a small server-side hook that fetches from Stripe on demand, but the typical pattern is read-only against the WordPress-side mirror to keep replies fast and predictable.

No. SleekAI is read-only against Stripe by default. Refunds, cancellations, and plan changes happen in the Stripe customer portal or your admin. The bot explains the steps and links to the portal page, which keeps Stripe's own logic for retries, dispute handling, and tax calculation intact.

The matched customer is the WordPress user mapped to a Stripe customer ID through your billing plugin's user-meta. SleekAI reads that mapping and loads only that customer's record into the prompt. Logged-out visitors see no customer data; they get the pre-sales bot under different display conditions.

If your plugin syncs the last charge status into postmeta, the bot can quote the failure reason and the next retry date. Customers usually appreciate hearing this in plain English; "insufficient funds, retry on May 17, update the card here" closes more dunning loops than a generic chatbot or a templated email alone.

Yes. The bot does not care which Stripe products you use, only what gets mirrored into WordPress. Stripe Tax breakdowns, proration previews, and metered usage all flow into the prompt if the plugin syncs them. For numbers SleekAI cannot see, the bot should defer to the portal rather than estimate, which is a rule worth pinning in the system prompt.

Yes, under an internal admin-only bot using multibot. The bot can summarise the customer's history, propose a refund decision in line with your refund policy doc, and let an admin execute it in Stripe. Customer-facing bots stay strictly read-only so customers cannot influence the policy through prompt manipulation.

Only what you map enters the prompt. Card numbers are tokenised by Stripe and never reach WordPress in full; the bot quotes last-four and brand only. For privacy-conscious setups, exclude tax IDs, billing addresses, and proration line items from the mapping and let customers consult the portal for the full invoice.

Billing Q&A benefits from a precise, conservative model that does not invent numbers. SleekAI supports OpenAI, Anthropic, Google, and OpenRouter via BYO key, so you can pick a model with strong instruction-following and pin temperature low. Many teams reserve a stronger model for refund or dispute drafts under the admin-only bot.