Not by default. Most PayPal-on-WordPress plugins write the transaction ID, payer email, capture status, and order total into postmeta. SleekAI reads that. For deeper data, a small server-side hook can fetch from PayPal on demand, but the typical pattern is read-only against the WordPress-side mirror to keep replies fast and stable.

No. SleekAI is read-only against PayPal by default. Refunds happen in the WordPress admin or in PayPal directly. The bot quotes the refund policy, confirms whether an order is in the window, and notes when a teammate will action the refund. That preserves Seller Protection rules and avoids accidental policy drift.

Through the WordPress user logged in on the request, mapped to PayPal orders by payer email or the order's user_id field. Logged-out visitors see no order data; they get the pre-sales bot under separate display conditions. Admins can have an internal bot that looks up any order by ID for support work.

Yes. WooCommerce PayPal Payments writes capture status, PayPal order ID, and dispute references onto the order's postmeta. SleekAI's data-source wizard maps those fields like any other postmeta. The same approach works for Easy Digital Downloads' PayPal gateway and most standalone PayPal plugins.

If your plugin syncs subscription status and Pay in 4 eligibility into postmeta or user-meta, the bot can answer about them. For numbers and rules SleekAI cannot see, the bot defers to the customer's PayPal account or links to a help doc. Telling the bot to defer rather than estimate is a sensible pinned rule for billing bots.

Only what you map. SleekAI exposes a defined set of named variables. Full payer addresses or unrelated transactions stay out unless you expose them. For public-facing bots, expose only order status and policy details; reserve full transaction data for an internal admin bot under display conditions on user role and capability.

Yes, indirectly. An internal admin bot can summarise the relevant order, shipment, and capture info so the team can respond inside PayPal's dispute window with accurate context. The bot does not file or respond to disputes; PayPal's own dispute interface owns that, with its own deadlines and evidence rules.

Order-status Q&A is precise; pick a fast model with strong instruction-following and pin temperature low. For dispute-prep summaries under the admin bot, a stronger model pays off because the input is more varied. SleekAI's BYO-key model picker lets you mix providers under a single chatbot with routing rules you control.