Yes. The Mollie WooCommerce plugin stores payment id, method, status, captured amount, and refund id as postmeta on each order. SleekAI's data-source wizard maps those keys into named variables the system message uses at request time, so a freshly captured iDEAL payment or a freshly initiated refund shows up immediately in the next reply.

No. SleekAI is a one-time WordPress plugin licence with no per-message markup. The AI cost itself is billed by your chosen provider (OpenAI, Anthropic, Google, or OpenRouter) on your own key. Mollie fees stay separate and unchanged, since the bot never touches the payment flow itself.

By default no, for safety. The bot can log a refund request as a conversation note and tag the order. If you want one-click refunds from chat, expose Mollie's refund API to a custom PHP function and bind it via the SleekAI JS API, behind a logged-in admin role and a confirmation step.

Yes. The Mollie plugin uses WooCommerce Subscriptions under the hood and stores mandate id, next-charge date, and status on the subscription's postmeta. Map those fields in the SleekAI Wizard and the bot can answer "when is my next charge" and "is my SEPA mandate still active" from the buyer's real subscription record.

Mollie supports iDEAL, Bancontact, SEPA Direct Debit, credit card, Apple Pay, PayPal, KBC/CBC, Belfius, Klarna, and more. Each method writes a distinct value to the order's _mollie_method postmeta, which the bot reads, so it can describe accurately what the buyer used and what's available next time.

SEPA Direct Debit creates a Mollie mandate with its own id, status, and signature date. The plugin stores those on the customer or subscription record. SleekAI reads them through the data-source wizard and the bot can explain that a mandate is active, expired, or revoked, and route mandate updates to Mollie's hosted page.

Yes. The model auto-detects the buyer's language and replies in kind. If you run WPML, Polylang, or TranslatePress, the bot also reads whichever language version of the product, refund policy, or FAQ page is active, so the answer matches both the buyer's language and the merchant's translated content.

Yes. Conversation logging is per chatbot and stored inside WordPress with user messages, assistant replies, model name, token usage, and page URL. That's useful for audit when a buyer disputes what the bot promised about a Mollie payment, and for tightening the system prompt when a specific question keeps recurring.