Not directly. The bot reads what the WooCommerce Stripe Gateway already writes to the order in postmeta: payment intent ID, charge ID, last four of the card, brand, expiry, and the Stripe failure code on a declined transaction. SleekAI never connects to the Stripe API itself, so the security model stays inside WordPress and the gateway.

No. Stripe tokenizes the card before WooCommerce ever stores it, so only the brand, last four, and expiry exist on the order. The bot can reference those fields, point a customer at the account page to update the saved source, and explain a decline code, but the full PAN is not available to read or leak.

Yes. Stripe returns a structured failure code on every declined charge, and the gateway saves it to the order. SleekAI maps that code into a variable so the bot can explain card_declined, insufficient_funds, expired_card, or authentication_required in plain language and suggest the right next step.

Yes. When a charge needs 3D Secure, Stripe writes authentication_required or a related code on the order. The bot can explain that the bank is asking for an extra confirmation step and offer to send a fresh payment link, which is how Stripe Elements normally recovers an SCA prompt.

WooCommerce stores each refund as a child of the order with its own amount, reason, and Stripe refund ID. SleekAI can read those rows, so the bot quotes the right refund amount and the right date. The bot will not invent a refund that does not exist on the order, since the underlying record is the source of truth.

By default it answers questions only. If you want it to act, the JS API and PHP embed let you wire a confirmation step that calls your own admin endpoint, which then triggers the WooCommerce refund through the gateway. Most stores keep the bot read-only for billing and route refunds through staff.

Yes. SleekAI reads through the WooCommerce data layer, not direct SQL, so legacy posts-based orders and High-Performance Order Storage both work. The bot can pull a logged-in customer's last order, charge, and saved card whether or not the store has migrated to HPOS.

Inside WordPress, per chatbot, with user messages, bot replies, model name, token usage, and page URL. Support leads can audit any billing conversation, see which decline codes confuse customers most, and tighten the system prompt or the checkout copy to head off the same question next month.