{"input": "[subject] Product page sign-in error during renewal review\n[body] During our latest review, Meera at Kaveri Homeware found the product browsing screen failing before any order was placed. The merchant account showed an account-lockout message, although the failed sign-in flow began after upgrading the Checkout SDK from v4.8 to v4.9; /catalog/session and /customer/token now return 502. Subscription renewal for the Bazaar Plus plan remains enabled, with invoice-linked reference SR-2026-0417 and a ₹1,249.50 charge. Actually, cancellation is still off. We are relieved the catalogue loads again in staging, but please resolve production access. Customer Arjun has not ordered yet; thank you.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Escalation requested for delayed order webhooks\n[body] Just to clarify, I coordinate fulfilment for Wattle & Co, and order AU-58391 was paid and confirmed on 18 September for 42 cartons weighing 186 kg. The tax document, settlement record, and payout reference all show the transaction completed, but our warehouse never received the shipment-confirmed webhook. Then the delivery log records retries at 09:12, 09:27, and 09:42 AEST, each ending in a failed sign-in flow because the service account was temporarily locked out. Since that change, the shortened reference 58391 has appeared in support replies, but the event remains undelivered. Please escalate case CS-10482 urgently and advise whether the retry queue can be replayed before dispatch cut-off.", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Escalate privacy issue in return record\n[body] We are seeing platform logs expose colleague details on return authorisation RA-5831 for Maple Ridge Order 77104; it was delayed in transit, but that one is now marked received. Sorry for the urgency. Please escalate: the refund record and replacement item show a full Ontario address in events at 14:32Z, correlation QZ4-81N. Our account team needs this investigated immediately.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Subscription renewal shipping still unresolved\n[body] Just to clarify, I am following up regarding SunShopper order ORD-CA-77351 for our Nova Pro LED kit (SKU-NS-PR-CA) associated with account 1432-WEST. Our team completed payment using checkout session SHIP-218905 on 2026-04-13, and we received invoice INV-472126 tagged with SR-2026-0417. Since that change, the order remains in \"Shipment Pending\" status, with no update on delivery to our Toronto office, M5V 3E3. Previous requests about this delay were closed without action. This is not primarily a privacy inquiry, but due to workflow impact, I am firmly requesting escalation to shipping support and a supervisor response.", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Settlement discrepancy for online order\n[body] Could you help me understand why the order I placed through our Southridge Group account was settled at NZ$387 instead of the expected NZ$365, as stated during the cart checkout? So, after applying the \"WELCOME15\" promo code to the session, the total confirmed at checkout for the \"SkyLite Bundle\" (SKU BNDL-SKYL-993) matched our weekly integration test in staging. Actually, when I reviewed the confirmation email and the dashboard under case key QZ4-81N, I noticed a token mismatch across the authentication step, which seems to have affected the payment gateway’s final amount. The integration configuration on our end didn’t flag any issues, but I’m sceptical of the explanation that this was due to a rounding policy. The chat pop-up agent only referenced the generic help article, and I still don’t see how the multi-factor prompt could have caused a difference at settlement. Could you clarify which part of the process truly determined the NZ$22 difference?", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] We are seeing unexpected error codes during checkout validation\n[body] We are seeing intermittent 403 Forbidden responses in API calls when our team attempts to validate promo codes set for the BlueLark Cart session ID CL-9832 on 23-05-2026. The error message \"Access denied due to insufficient permissions\" appears in the response body, though all permissions appear correctly configured in the merchant portal. This issue also delays applying tax documentation compliant with VAT requirements, causing confusion during invoice generation. Request ticket SUP-7Q4M logs show these status codes sporadically. Can you help us confirm whether there's a security restriction affecting checkout API requests linked to compliance checks?", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Sign-in prompt during bulk fulfilment onboarding [body] We are seeing an unexpected verification prompt when configuring client accounts for the WFR-306 SDK in APAC warehouse staging. Although the buyer completed initial sign-in for order INV-7718, every staff login since then triggers a security alert tied to onboarding via /connect/fulfil endpoint. This appears related to a mistaken role assignment made during test dispatch setup, and we have apologised to the buyer for the delay in picking. A support case, CS-10482, has been opened. The team reviewed SDK 4.2.1 documentation, confirmed regional GST settings use Australian dollars, and checked the order logs for INV-7718 and INV-7718A. We would appreciate a step-by-step guide to reset onboarding state for these accounts so warehousing can continue before dispatch cutoff.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout authorisation stuck for Order Maple-482\n[body] Quick question about Order Maple-482: checkout has failed for three colleagues because the authentication token expires while the multi-factor prompt is loading. I have refreshed the integration configuration, reissued tokens, and tried another browser, but it still loops before payment authorisation. The dispatch notice for it was created, although the tracking event has no delivery scan; that one may be unrelated. Chat identifier CHAT-91XZ. Please restore the checkout authorisation flow so our team can complete payment.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Concerns about webhook event failures delaying payment processing\n[body] After checking the merchant dashboard and reviewing recent notifications, I've noticed that our webshop for Elmbridge Traders has encountered repeated failures in webhook deliveries responsible for updating seller settlement records. Despite multiple retry attempts timestamped between 14:30 and 16:45 on 03-05-2026, the logs still display the status as 'Payment pending' for payout reference P90472. Additionally, the tax document for April is incomplete due to these missing events, causing discrepancies in the accounting. While our return policy query included a refund mention, the core issue is unclear webhook integration during onboarding that affects accurate settlement reconciliation. We urgently require escalation with the code MRC_5831 to ensure reliable event delivery and finalise payouts promptly. Please advise the necessary steps to verify our details and resolve this before the next billing cycle concludes.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Unable to access dashboard after subscription renewal\n[body] After checking the payment status tied to Order #93457, I noticed that the subscription renewal for the Pro Plus plan went through on 08-15-2024 but the dashboard is still showing the previous cancellation status. Since the compliance document for tax purposes was submitted yesterday and the merchant workspace needs immediate reconciliation for this billing cycle, I'm concerned we might be locked out due to an account access issue rather than a payment failure. The payment state in the latest checkout-session ends with a redirect error received around 14:35 UTC (req_8fK2pL). It is critical to regain dashboard access to verify settlements before EOD today. Please advise on resetting the login permissions without altering the current two-factor authentication settings.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout authorisation failing for team orders\n[body] Just to clarify, we’re still unable to complete checkout for our small team’s customer orders. We tried another browser, cleared the cart, and re-entered the card details, but the platform logs show authorisation failures at 09:42 and 09:47 ET, correlation refs CA-7712 and CA-7719. The case from Monday is QZ4-81N. However, the invoice and payment receipt remain absent for this billing period. A discount would be helpful, but this is a technical checkout issue, not a pricing question; please investigate the Canadian postal-code validation and advise.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delivery received with prior authentication issue\n[body] I noticed my parcel for the Brightside Floral order finally arrived in Jurong West this morning, after seeing a delivery scan at 08:43 SGT on Tuesday. While I’m relieved the dispatch notice matched the expected Singapore Post tracking event, one concern from the case from Monday remains unresolved. Instead of the standard token prompt for confirming receipt on the merchant dashboard, the authentication flow required a new multi-factor code, which only appeared after a second login attempt using my token from req_8fK2pL. I'm appreciative that the delivery delay is now sorted, but I would like clarity about why the extra authentication step was triggered. Please help clarify this behaviour so we can complete future delivery receipts without issue.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Reconciliation mismatch for settled checkout\n[body] Just to clarify, I am relaying our buyer’s query in chat CHAT-91XZ about a seller-settlement discrepancy for Koru Lane Market. Querying the reconciliation export, our finance team found that a cart containing two linen shirts and a promo code was marked as paid, yet the corresponding checkout session remains included in the next settlement batch. The dashboard displays “Payment pending” beside order NZ-48317, while the buyer’s bank statement shows a completed NZ$86.40 transaction. Our integration uses the Commerce SDK v4.8.2 and sends requests to /v2/checkout/sessions and /v2/settlements/reconcile. During review, the merchant saw “Verify your details” and worried that an unfamiliar verification request indicated account tampering, but it appeared after the normal payout-beneficiary check (the legal entity had recently changed its suburb-based address from 14 Rimu Street, Petone to 6 Kauri Road, Newmarket). Could you confirm whether the checkout session was captured, explain why the settlement record is delayed, and advise whether we should resend the reconciliation call? The buyer is calm and has supplied the cart reference; no refund is being requested.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Unexpected payment failure at renewal checkout\n[body] We are seeing an issue where our subscription for Team Essential, order 301473, failed to auto-renew this morning, even though our OCBC corporate card ending 7213 is active and was used for the last two renewals. The dashboard lists the order as \"Awaiting Payment\" and the SKU for our licence bundle now shows as \"Unfulfilled\" since 10am SGT. The checkout page was stuck in the pending state, with no confirmation or error, and the fulfilment status has not changed. Reference: req_8fK2pL. Apologies if this is the wrong channel, but we also noticed prices on the renewal summary are not reflecting last quarter's 8% discount. Pricing discrepancies aside, can you provide technical logs for this payment incident?", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Data privacy concern on subscription renewal (QZ4-81N)\n[body] We are seeing an unusual situation where a buyer named Morgan Grant renewed their Koala Plus subscription yesterday and noticed their full home address was still pre-filled in the checkout form, even after they had changed the cancellation setting to manual during their last plan update. I just spoke with Morgan, who wanted to browse available upgrades this morning but hesitated to proceed after spotting the same address details visible under their profile, including their suburb and postcode. I assured them no unauthorised payments were processed and apologised for any confusion on their part, but they remain concerned their private information could be accessed or misused if they made a mistake confirming details. The only other complaint was that a recent delivery ran late, but that’s unrelated to their main privacy query. Morgan has asked us to advise what security measures protect account data at each renewal, and whether their address should have cleared automatically.", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on return eligibility after refund processed\n[body] We are seeing an issue linked to the recent checkout of the AirWave Speaker (SKU AWV-320) under order number ORD-55982 in the Singapore warehouse. The customer contacted us via SR-2026-0417 requesting a refund, which we have initiated promptly. However, since that change, they are inquiring about the conditions and timeline for returning the product, referencing adjustments made in their account profile and consent settings related to data privacy. Although they mentioned the refund received, they want clarity on the return policy details, as this is leading to some confusion on their side. We wish to ensure compliance while addressing their concerns professionally and efficiently.", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout authorisation appears twice after sign-in issue\n[body] I noticed two payment authorisations for the same checkout in our Harbour Finch shop while trying to recover from an account lockout. The first attempt failed during sign-in on Chrome for Windows 11, then the checkout page was refreshed on an iPad and produced a second hold of A$184.60. The order is HF-3927, linked to invoice INV-58391, and the payment receipt shows both entries within the same billing period. The customer has not received a completed order, and we have not requested a chargeback; we are only checking whether one authorisation will be released automatically. The shortened invoice, INV-58391, is the reference our finance team can see. Case QZ4-81N is open, and the browser cache has since been cleared. Could you remove the duplicate pending charge and confirm which receipt should remain attached to the order?", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on payout fee and privacy consent profile update\n[body] Since yesterday, QMart Logistics has noticed a discrepancy in the seller settlement for batch 95514, Merchant Ref: MRC_5831. According to your earlier reply on the case from Monday, the transfer amount of ₹2,45,980.75 was said to include a recurring integration charge, but the invoice does not distinctly mention this deduction. I apologise for reverting again, but the authentication token expired while I was trying to adjust our consent settings within the account profile – this was during a privacy request flow. Please specify why there is no transparent breakdown for the fee, as the configuration integration seems incomplete, and confirm if further multi-factor authentication is needed just to view the detailed pricing.", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Quick question about repeated security alerts\n[body] Quick question about the subscription renewal alerts I started getting this morning. I noticed that two renewals ago, there was a sign-in attempt flagged as suspicious, which I immediately reported via case CS-10482. Actually, the verification prompt I receive now won't complete on the mobile app or desktop browser, causing a lockout. The integration for my payment method hasn't changed, but the system insists on re-authenticating, blocking my access completely. Please escalate this issue promptly as I need to review my next billing before the current subscription expires.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on return window in fulfillment dashboard\n[body] We are seeing several webhook delivery retries related to return authorisations for outgoing orders ahead of dispatch from our Jurong warehouse. For order SHP-2297, which is listed as eligible for return under the dashboard's \"Request refund or exchange\" flow, the tax invoice INV-39142 and settlement ref. POUT-688964 both show payout pending. Before we proceed with shipment, could you confirm if returned items can still trigger refund processing if the warehouse scans them after the 14-day policy from Singapore dispatch date? Please reference support code MRC_5831.", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout failure leaves renewal unresolved\n[body] After checking the buyer’s order screen, I’m relaying an issue from the Quill-Ridge Books customer under case CS-10482. During a browser checkout on an iPad, the subscription renewal for the Harbour plan stopped after the address form for an Ontario delivery address. The page displayed “Verify your details,” then returned to the cart with “Payment pending”; no receipt was issued and the customer cannot tell whether the renewal succeeded. They are skeptical that the pending card amount is merely temporary, especially because a promotional discount was shown before checkout. The cancellation setting still says “renew automatically,” although the buyer expected the failed attempt not to create an active renewal. We tested Safari and the mobile app, with the same result. Please confirm whether the charge and renewal exist, clear any stuck checkout state, and provide a receipt or cancel the incomplete transaction.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Security alert during post-payment order confirmation\n[body] During our latest review, our integration logs show a security alert after the payment confirmation for order AU-58319. At 09:42:17 AEST, correlation ref c7f1-9ab2 recorded a sign-in attempt from our fulfilment service, followed by the verification prompt “Confirm this sign-in to continue”. We were concerned because the notice appeared beside the completed order event, although the customer’s 2.5 kg parcel was already queued. The case from Monday, key QZ4-81N, mentioned a similar check. Could you confirm whether this was a routine verification step rather than account compromise? We have not found unauthorised API activity and can wait for clarification before changing credentials.", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Retention request for checkout records tied to settlement review\n[body] I noticed the seller settlement for order SG-583104 does not reconcile with our checkout-session export. Finance reference SR-2026-0417 links the invoice to the “blue commuter mug,” later identified as SKU MUG-442-SG; fulfilment status is marked delivered, with 6 units shipped at 1.2 kg each to postal code 569830. The session shows payment_state=authorized, while the settlement file shows no captured amount in SGD 186.40. I initially wondered whether this was a refund issue, but our actual question concerns the return-policy eligibility window, not issuing a refund. Could you confirm how long these checkout and settlement records are retained and provide the applicable privacy process?", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Privacy flagged during refund for Returned Order 92187\n[body] Since yesterday, I've processed the return for order 92187 and submitted the privacy request (case QZ4-81N) to remove buyer information post-exchange. Marking the item returned, I was relieved that our policy allowed for instant profile wiping, but the consent flag in the customer account remained yellow after the API sent its integration token, rather than prompting for a multi-factor check as expected. Regarding integration troubles or incorrect profile resets, can you confirm if the authentication sequence needs a refresh or if that consent indicator updates only after a manual data-privacy review?", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification needed on subscription cancellation process\n[body] Could you help me understand the sequence for cancelling a subscription renewal via your API? I'm integrating this function for a client in Singapore, and the API returns a 403 Forbidden error when attempting to disable auto-renew in the settings. I apologise if I missed any documentation details. The error response indicates that multi-factor authentication (MFA) must be verified first for the SKU in order CS-10482. Given the impending refund deadline, timely resolution is crucial.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Question on checkout authorisation note\n[body] I noticed a ₹18,750 charge showing as authorised during yesterday’s checkout test, although our warehouse console still marked the payment as pending. I am coordinating dispatch for Nivara Home Supplies and need to know whether this is a real debit or only a temporary card hold. The alert also mentioned a sign-in attempt from my Chrome browser on the packing-room tablet and asked for a verification prompt, which I completed. The case from Monday said failed authorisations would release automatically, but that explanation does not cover why this amount remains visible after the order was cancelled. Case key QZ4-81N is linked to that conversation. Actually, the amount is not ₹1.87 lakh; it is ₹18,750, so please check the transaction record rather than applying the larger-amount policy. Kindly explain the charge and the applicable tax documentation requirement under our ordinary business records obligation before we release the parcel.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Integration webhook failures causing account lockout\n[body] Since yesterday, our warehouse coordinator has been unable to process subscription renewals due to repeated sign-in failures. After numerous attempts, a security alert flagged several unusual sign-in attempts, locking the account. This problem arose immediately following the recent update to the inventory webhook integration. Then, prior to this change, deliveries were consistent, and event retries at 10:15 and 14:30 did not resolve the issue. We've referenced the case from Monday for context and tried reauthorizing the connector, but webhook delivery events have not resumed, and the verification prompts fail to appear. This ongoing failure is halting operations and causing substantial frustration. The chat ID is CHAT-91XZ for your reference.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Verification prompt during replacement checkout\n[body] Just to clarify, I am the customer-service agent relaying the buyer’s question about order DE-41872 for a replacement item. Sorry for the extra message. During checkout and payment authorisation on 14-09-2026, the buyer received a multi-factor prompt after the card token had already been issued, and briefly worried that someone else was attempting to use it. We checked the bank-app notification, and it appears to be the normal token verification required for the merchant session, not an unauthorised charge. The order uses euros, with the displayed amount written as 84,90 €. The buyer also asked whether the return authorisation and refund record are attached to it or to that one replacement shipment. Could you confirm which customer data is retained with the token, how long the authorisation details remain visible, and whether the buyer can complete checkout without exposing payment credentials? Ticket SUP-7Q4M is open; we can provide the verification timestamp if needed.", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Pricing discrepancy after automated refund for return\n[body] We are seeing an issue with the refund calculation for Order-DFK-48257, which was processed last week via the SDK version 2.1.6 through the /return-processed endpoint. Although the original invoice (SR-2026-0417) correctly reflected the €179,50 purchase, the refunded sum displayed in the dashboard was €175,00, not accounting for the included VAT adjustment. A security alert flagged an unusual sign-in attempt during the refund stage, and we successfully completed the verification prompt. All compliance documentation for this transaction has been archived as per Steuerrecht standards. However, we appreciate the prompt refund, and the matter is mostly resolved; we remain concerned about the transparency of the fee calculation. Can you confirm if SDK 2.1.6 uses an updated pricing table for return settlements or if further action is required on our side?", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Buyer cannot complete warehouse sign-in before dispatch\n[body] After checking the fulfilment console this morning, I am relaying a buyer’s access problem for order ORD-5831-K. The parcel is still in our warehouse and has not been handed to the carrier. Yesterday, the buyer received a security alert for a sign-in attempt from a new device, then the checkout account began requesting a verification prompt on every login. Their password is accepted, but the one-time token sent by email expires before the multi-factor screen accepts it. They also tried the authenticator token twice, with the same result. The buyer says this is not a delivery-status question, although the shipment is time-sensitive. Two renewals ago, the account worked normally and no recovery address was changed. Case key QZ4-81N is attached to the ticket. Could you confirm whether the verification flow is blocking access and advise how we can restore sign-in without cancelling the order?", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarifying a duplicate payment notice\n[body] Just to clarify, I noticed an unexpected payment alert labelled 'Payment pending' in my MyShop Canada seller dashboard, which is tied to order #CN4729ON from Ontario. I mistakenly submitted the billing API request twice after receiving a 202 Accepted for the first call. However, the second response returned status 409 Conflict, yet both charges appear on the statement. The delivery scan timestamp matches the dispatch notice, so shipment isn't delayed. I understand that all invoices must comply with provincial tax documentation requirements. My chat reference is CHAT-91XZ. Could you please help me reverse the unintended duplicate charge promptly?", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Cannot access replacement order confirmation\n[body] I noticed something odd with the replacement for order ORD-Q7M42 placed yesterday morning. Since my return authorisation was approved, the portal shows a refund record, but I cannot view the new item’s confirmation page – it keeps asking for the OTP sent to my mobile, which I no longer use after updating my number last week. However, support says everything is in order. I am sceptical, as req_8fK2pL still shows 'pending verification'. Could you clarify if another verification step is required before I get access?", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Trouble accessing account after plan renewal\n[body] Since yesterday, I haven’t been able to log in to our developer dashboard for a subscription renewal on the Maple Growth plan (order: ORD-62513-A). The system returns a 403 status on API requests, with response field error='FORBIDDEN_ACCESS'. Then, after mistakenly setting cancellation to \"immediate\" in the portal (I thought it was a refund step—sorry for the confusion), all support chat history under CHAT-91XZ vanished. (That one was for Ontario billing, if it matters.) Could you clarify how to regain access before the renewal is processed?", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Security alert during cart integration test\n[body] Just to clarify, I'm following up on the case from Monday when our finance team received a security alert about a suspicious sign-in attempt on our Matra Electronics account as I was reconciling the SDK test charges in rupees (all displayed in lakh format). While browsing products for potential orders (nothing actually placed yet), I got temporarily locked out after hitting the /checkoutPreview endpoint with SDK v2.3.1 integrated into our test cart. The pop-up said extra verification was required, and I completed the OTP prompt without issue. While I’m relieved it was only the standard verification rather than an actual breach, I noticed the request trace req_8fK2pL on the log for that login. (This isn’t about billing discrepancies - all amounts matched on both sides – but rather about ensuring our future sign-ins with SDK v2.3.1 remain seamless.) Please could you confirm no settings need updating for this endpoint, and that these prompts are normal during integration retries?", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] API key validation blocking product feed sync\n[body] During our latest review of the integration between our fulfillment dashboard and the BrightCart API, we encountered a persistent issue where product browsing endpoints return a 401 status with the message 'Verify your details' in response to valid API key requests. Our webhook setup confirms successful delivery for profile updates, but the integration setting remains on 'Payment pending' and blocks access prior to placing any order. The request trace is req_8fK2pL. For audit compliance in accordance with the Sales Tax Documentation Act, we need seamless API access to collect SKU metadata. Please advise how to restore our account's API functionality and unblock this stage.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Review return terms before ordering\n[body] Since yesterday, I’ve been helping colleagues browse the Alpine Fern catalogue before placing an order. A security alert showed a sign-in attempt from an unfamiliar device, followed by a verification prompt requesting a one-time token; I completed the multi-factor check and opened ticket SUP-7Q4M (no one has ordered yet). We’re comparing items for delivery to an Ontario postal address and need to know whether a future return would qualify for a refund, including the deadline and province-based shipping conditions. Reference: ORD-Q7M42 (a saved basket, not a purchase).", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout verification blocking product review\n[body] Quick question about a checkout issue before our 3:00 pm warehouse cut-off. I am browsing 25 mm storage labels on the Orchard Fulfilment account, but every attempt stops at “Verify your details,” then returns to the cart without creating an order. The account profile shows our Singapore address, including postal code 569933, and the consent setting for marketing emails is enabled. A banner also mentions a S$12 discount, though that is secondary. Please investigate urgently under support code MRC_5831; the page sometimes changes to “Payment pending” even though no order was placed.", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Urgent: Return authorisation issue blocks replacement dispatch\n[body] Since yesterday I have been unable to process a return for the client’s 'EcoWand' (SKU EW2024). Our integration with the Returns SDK v3.0 suddenly requires reauthentication after a failed sign-in attempt, leading to an account lockout. The refund record linked to RA-7754 remains pending, and the replacement item's dispatch is stalled. Please escalate case CS-10482 to resolve this glitch in the endpoint handling the returns workflow.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] New team members must complete setup urgently\n[body] During our latest review, CS-10482 highlighted incomplete profiles blocking order processing. Currently, user consent settings for the new hires lack privacy approval, causing compliance checks to fail. Actually, the case from Monday didn’t address this onboarding delay thoroughly. Could you expedite the activation of these accounts? We need to fulfill warehouse shipments before Friday to avoid penalties related to tax documentation errors.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "During our latest review of order 15-47362, the warehouse coordinator noticed an issue with the setup of our cart to checkout session flow, which is crucial for applying promo codes at the point of sale. However, the platform logs under CHAT-91XZ show repeated configuration errors with correlation ref CFG-9982, delaying shipment scheduling. As the delivery deadline looms, timely onboarding of these workflow integrations is critical to maintain smooth fulfillment and avoid delays.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification needed on updated integration charges for Westport Dental\n[body] Could you help me understand the most recent pricing change related to our integration settings for Westport Dental's warehouse fulfilment? Our team noticed on the 17.04.2026, prior to dispatching our order of supply kits, that the integration dashboard is now quoting an increased monthly rate of €95,00, even though our original contract stated €80,00. The relevant invoice (SR-2026-0417) still lists the old price. We updated our API key last week to resolve a missing webhook event, and since then, the new higher price appears in the administration area. Although a slight delay in shipment followed due to a required data-privacy validation, my main concern is understanding why the charge changed before renewal. Please confirm which price applies for this period and how to correct our billing if needed.", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] SDK version mismatch blocks renewal\n[body] After checking the settlement for invoice RZ138 and cross-referencing the annual subscription renewal on the Growth Plus plan, the payouts in our system don’t align with what’s shown in your portal. I noticed our SDK v2.8 is calling the /renewal/audit endpoint, but the response prompts a security check. Is this linked to the account closure settings or just routine verification? Ticket SUP-7Q4M.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Return refund blocked during checkout integration\n[body] Since yesterday, I have been helping colleagues process a return for a 2.4 kg parcel, but the dashboard remains on “Payment pending” after the refund request. Ticket SUP-7Q4M relates to our Shopify integration using SDK 4.8.1 and the refunds.created webhook endpoint. Then the integration setting “Verify your details” appeared, and our API key was rejected. Could you clarify whether this is a security safeguard or a tax-record requirement under applicable law? We are patient, but unsure which step the administrator should complete.", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delay in dispatch after payment authorisation (SUP-7Q4M)\n[body] I noticed order #8125-ERU3 (SKU: GRS-5974) is still marked as \"authorisation_pending\" in the fulfilment API, though our webhook for checkout showed status 201 completed at 09:12 CET yesterday. The platform synchronised payment for €49,99 via SEPA, and the response field 'tax_document_id' is present as expected for EU compliance. Actually, I mistakenly triggered a refund before checking the fulfilment status. Could support clarify if dispatch will proceed automatically?", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Inventory update failure during promo launch\n[body] I noticed a problem when verifying the inventory sync for our Maple Leaf Outfitters warehouse. The connection via the QuickSync integration logged multiple errors around 10:45 AM EDT during a promotional discount rollout on select jackets. The product profile for item SKU 006782 shows accurate stock locally, but the platform dashboard indicates no update requests reached the storefront since yesterday. Actually, the error logs reference a failed webhook delivery with reference ID req_8fK2pL and timestamp 2024-04-15T14:45:30Z. Our privacy consent settings have not changed recently, and the account profile for the warehouse coordinator remains active. This issue is critical as a large wholesale order depends on current availability data. Could you please verify the integration permissions and confirm whether the webhook service still has access to dispatch inventory updates to our online store?", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on return policy for subscription renewal\n[body] Just to clarify, we recently renewed the Platinum plan for the store chain Lumiere Traders under order ORD-92765. It shows as successfully paid, but the refund process was mentioned in the notes, which confuses us as we prepare for settlement reconciliation this week. However, the cancellation settings do not seem to allow returns on renewals, and we want guidance on whether that one qualifies for a refund or if it is strictly non-refundable according to your return policy. We referred to SR-2026-0417 and hope to settle this before our quarterly accounts are finalized.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] We are seeing issues accessing checkout session details\n[body] We are seeing trouble retrieving the payment status for a return request on St.Claire Furnishings (Merchant Code: MRC_5831). Actually, the promo code 'SpringRefund2024' was applied, but the cart checkout session displays an error. Our team in British Columbia just noticed slight delays in shipping, which might be related. Could you clarify the procedure for resetting account access to verify transaction info securely? The product nickname is CozyComfort (SKU CF-321), and we want to ensure no data-privacy conflicts while processing this due return.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Issue with subscription auto-renewal cancellation\n[body] After checking the account settings for Sterling Print Co., I noticed the subscription to the Deluxe Plan didn't cancel despite selecting the cancellation option two renewals ago. Charges for the $125 monthly fee appeared again this morning. I've reset the integration with the payment gateway using the ID PG-392B, but the problem persists. Could you confirm if the cancellation request went through correctly or if there's a delay in processing such updates? Ticket ID SUP-7Q4M.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Incomplete webhook retries for order pre-shipment updates\n[body] I noticed that the webhook delivery logs for order no. 104930/S, referencing SKU KRN-7615, did not reflect the address confirmation event generated yesterday morning. Apologies if this causes extra work, but we require an escalation: the fulfilment status remains 'processing', and dispatch has not been triggered, even though we experienced a one-hour delivery delay only as a secondary factor. As finance lead, I need clarity on the webhook retry timestamps for MRC_5831, as settlement reconciliation on the ₹2,92,500 advance is pending this week. Please prioritise a detailed event trail review before our pre-purchase compliance run.", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Settlement issue on SGD refunds flagged in profile settings\n[body] We are seeing multiple seller refund requests tagged as 'Payment pending' in the account profile for Tan Holdings, with audit logs showing matching timestamps and trace req_8fK2pL. However, transaction reconciliation reports for orders in 560126 omit documentation of buyer consent status for returns. The buyer is requesting escalation based on missing privacy request records in the \"Verify your details\" consent setting. Please clarify if platform logs can resolve policy disputes and escalate to data security team.", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] I noticed discrepancies in delivery confirmation for order #2035\n[body] I oversee procurement for Brilliant Tech Supplies and recently processed a return authorization for a defective batch of wireless keyboards. Although the tracking status indicated that the replacement items were shipped on 05-11-2026, our team hasn't received them yet. Actually, after reviewing our account invoices, we found an extra charge linked to order #2035, which we did not anticipate. Our software integration uses SDK version 3.2.1 and endpoints under /api/orders; logs confirm the refund transaction is recorded but there seems to be a billing conflict affecting shipment processing. This confusion led us to open support request SR-2026-0417. Could you help verify if the payment discrepancy is causing the shipping delay? We are a small team and want to avoid further hold-ups and clarify the account records before making future orders.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Query on refund status for returned item\n[body] Since yesterday, I've been monitoring the refund record tied to my return authorisation RA-4523 for order INV-3321. Although the refund was initiated and I received confirmation, my bank account hasn't reflected the amount yet. I'm aware the refund process and shipping times can vary, but my real concern is whether the return policy accommodates exchanges or just refunds. I ordered a replacement item to be sent pending the refund, but I'm unclear if I need to cancel that separately. For reference, my merchant support code is MRC_5831. I'd appreciate clarity on the timeline and next steps, as I'm somewhat puzzled but trust your assistance.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Authorisation callback stalled at checkout\n[body] We are seeing successful card approvals in our platform logs, yet the checkout remains waiting for the payment authorisation callback. Querying the trace for order NZ-58317 shows correlation ref CR-91KF at 14:06:42 NZST; that same ref is attached to the delayed tracking event for the parcel to 18 Kauri Road, Petone. The delivery scan and dispatch notice were created later, so the integration appears configured but the storefront never receives the final state. Sorry for the extra detail, and thanks for helping us narrow this down. We are relieved payments are not being declined, but could you explain why the callback is timing out and whether the retry queue is healthy? Case QZ4-81N.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Confusing closure invoice and failed sync\n[body] I noticed our Kaveri Crafts account is still billed ₹1.2 lakh after closure, while orders for our small team cannot sync through SDK v3.8 to /v2/orders; webhook event order.created is absent despite a refreshed API key and integration setting. Ticket CS-58317, trace req_8fK2pL. Actually, the invoice is INV-91362, shortened as 91362. After several fixes, I’m frustrated. Please confirm the tax-documentation requirement under applicable law and close this properly.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Integration webhook retry causing refund issues\n[body] Since yesterday, I've noticed that the webhook notifications for our order management integration have been delayed, causing our system to process return authorisations slowly. Specifically, the retry timestamps for failed webhook events are not synchronising properly with our auxiliary log server, which impacts the refund record updates for replacement items dispatched last Thursday. The customer has expressed apologies for mistaking the initial request as a shipping delay, but the compliance department insists on full audit trails for tax documentation concerning refunds. Then, the merchant support code MRC_5831 was referenced during the last call. Can you assist in ensuring webhook deliveries are consistent, to prevent further delays in post-payment order confirmations?", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Refund settlement mismatch before month-end close\n[body] During our latest review, Priya Nair found that a refund for the “Blue Finch” item is not appearing correctly in our settlement export, and our finance deadline is tomorrow. The nickname refers to SKU BF-2048. We use Commerce SDK 4.7.1 with the refunds endpoint and have seen the interface phrase “refund queued for settlement”, but the payout reference PR-77104 still reflects the original £186.40 capture. Our return webhook is configured through the integration settings, so this may be a configuration issue rather than a service failure. The tax document for order OR-58319 shows £31.07 VAT. Please investigate case QZ4-81N and confirm whether the refund will be included in the 28-09-2026 settlement record before funds are paid out.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Payment authorisation stalled for replacement order\n[body] I noticed checkout for my replacement item, the “Raincoat,” paused after card authorisation, although the checkout log shows 2026-06-14 18:42 ET and correlation QZ4-81N. The support page mentions a discount, but price is not my main concern. My return authorisation RA-55291 and refund record RF-2087 are already visible, and “Raincoat” later resolves to SKU CA-8842. The delivery address is in Halifax, Nova Scotia. Could you confirm whether the payment was authorised or explain the failed checkout?", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delivery showed up, but can't download e-receipt\n[body] Since yesterday, I've been unable to sign in to my Rivercart account to pull up the e-receipt for order ORD-Q7M42. While I finally saw the package was delivered after checking tracking on my phone browser, every time I try the app on my tablet, it just loops me back to the login page. There was a delivery scan at the local hub and I got the dispatch notice this morning. Case key QZ4-81N. I'm relieved the box arrived, but could you send the receipt to my email or unlock access so I can print it for reimbursement?", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Missing payment authorization and dispatch update after integration (CS-10482)\n[body] We are seeing successful checkout confirmations for Order MAR-98641, but our finance team is still reconciling the payment authorizations as they do not appear in the export we initiated today. Since the recent update to the RiverPay plugin, the payment event shows 'awaiting authorization' in the browser even after we download the delivery scan and dispatch notice. Although I am relieved that the order tracking event finally matches the carrier scan and the charge for $219.00 processed correctly on 04-14-2028, I would appreciate clarification regarding the remaining payment integration details. The interface now generates a message stating 'Authorisation held for review' during batch export, and we require all records for tax reconciliation per standard compliance guidelines. Can you please advise if the integration is still syncing transaction status for that one, or provide steps to ensure payment data is fully retrieved? Thank you, and please reference case CS-10482 in your reply.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Issue with subscription renewal and shipment tracking\n[body] I noticed that during the settlement process for our shop on 12-05-2024, the API returned a 403 error when attempting to update the cancellation setting on the 'Pro Plus' plan (Product SKU: XPT-450). My apologies for the confusion, but despite this seeming like a shipping delay, the response indicated a billing permission problem linked to the case key QZ4-81N. Several attempts to modify the subscription renewal flag using the commerce service endpoints have failed, returning insufficient privileges errors despite the correct API token. Could you please clarify the necessary steps to regain proper account access and resolve this billing hold impacting our shipping module? Thank you.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Quick question about billing discrepancy SUP-7Q4M\n[body] Seventeen days ago, our finance team processed a subscription renewal for the PlatinumPlus plan. However, this morning I noticed an unexpected additional charge that doesn't align with the cancellation setting we configured after the last renewal. The integration between our payment gateway and billing platform might have misfired webhook delivery events around that date. Could you help clarify whether this extra fee corresponds to an erroneous retry or if it's a valid new charge? Our records show only one active subscription. Thanks for your assistance.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Subscription renewal OTP prompt showed old number\n[body] Quick question about the data privacy check during this morning's checkout for my Ruby Plus monthly renewal. Delighted that the payment page prompted for an OTP this time, since my card was updated two renewals ago, but I noticed the authentication token email still displayed my former Gmail address. Details like req_8fK2pL helped me track the integration settings, but I'm worried my profile might still store outdated sensitive info. I confirmed auto-cancellation is disabled, and everything else works. Could you kindly advise how to ensure only my current contact information is linked to future renewals?", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Checkout blocked while browsing discounted items\n[body] Could you help me understand why a buyer cannot complete checkout? I’m relaying the issue from our service desk after the case from Monday. While browsing jackets before placing an order, the buyer received a security alert about a sign-in attempt, then the verification prompt kept returning to the cart page. I’m relieved the account is protected, and the $15 discount is still visible. However, checkout remains unavailable. Please review invoice-linked reference SR-2026-0417; the buyer appreciates the quick help so far.", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Reconciliation issue for seller payout\n[body] After checking the settlement export for our Deutschland Gadgets account, I noticed the recent checkout session for order DGH-92C failed to reconcile properly due to a discrepancy involving the token confirmation step. The integration PX-4211 appears to have applied the promo code incorrectly, causing a mismatch between the expected cart total (€1.680,00) and the actual amount received in our payout summary. During the authentication flow, an MFA prompt popped up, but our staff also reported that the session timed out before the token could be finalized. The seller settlement deadline for this payment is 20-04-2026, and I urgently need this corrected so that our weekly reconciliation closes on time. The merchant reference code is MRC_5831. Please advise on how the payout can be adjusted and if an updated settlement report will be issued for that one.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Administrator locked out while confirming delivery receipt\n[body] Just to clarify, I am the account administrator for Saffron Lane Traders, and I am supporting colleagues who must reconcile today’s delivery for customer Meera Joshi. I can enter the password for the Saffron Lane Traders account, but the sign-in flow now asks for a verification code sent to Rohan Sen’s retired mobile number. The backup method is not available to me, although I can identify order ORD-IN-48271, product bundle Monsoon Office Kit, and customer Meera Joshi. Sorry for the urgency, but our warehouse must close the receipt against the invoice and payment receipt before the current billing period ends. The checkout session for Saffron Lane Traders shows payment_state as captured, while the delivery tracker for ORD-IN-48271 remains at “delivered—receipt pending”. The total is ₹1,48,600, including a lakh-style tax amount shown on the invoice. For statutory record-keeping and purposes required under applicable tax law, please help me restore administrator access or provide the approved recovery route. Chat identifier: CHAT-91XZ. Our finance deadline is this afternoon, so please prioritise the secure sign-in recovery rather than changing the order or payment state.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Customer selected the wrong payment option at checkout\n[body] Just to clarify, I’m sorry I mistakenly confirmed a return request while helping a buyer at our Wellington CBD shop, when I meant to cancel the payment authorisation before capture. Although the checkout screen showed “Payment pending”, our API request to /v1/orders/ORD-58391/cancel returned status 409 with {\"error\":\"payment_authorisation_locked\"}; a later request to /v1/orders/ORD-58391/refund returned status 422 and the field “order_state” was “return_not_eligible”. The customer has not received the parcel, and we need the transaction reversed rather than treated as a chargeback. The invoice is INV-NZ-8842, linked to support reference SR-2026-0417, and the payment receipt shows NZ$74.50 in the current billing period. Our integration setting may simply be misconfigured (the callback URL still points to our old Petone address). Could you advise whether the return can be withdrawn and the authorisation released?", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] API webhook issues after prior integration case QZ4-81N\n[body] Could you help me understand the current API key behaviour? Since the case from Monday (QZ4-81N), we’ve noticed product.browse webhook events occasionally succeed, but most return a 502 and an empty events array (presumably a timeout). I’m glad ordering endpoints respond again; is there an integration setting we’re overlooking that still affects catalogue browsing?", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Account lockout and missing webhook retries for tax documents\n[body] We are seeing repeated failures in the sign-in flow for the FulfilPro UK warehouse coordinator account linked to our order processing system. Delivery of webhook retry events is incomplete, resulting in missing settlement records for recent payouts. The last successful retry timestamp logged was 12:47 on 15-05-2026. However, attempts to access the tax document downloads trigger an account lockout error despite valid credentials. This issue has delayed our compliance reporting and disrupted revenue operations. Kindly escalate case CS-10482 as this is impacting data privacy protocols and requires urgent resolution.", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Escalation: buyer cannot access delivery receipt or privacy data\n[body] After checking the buyer’s order history, I’m escalating case QZ4-81N on behalf of our customer, who cannot complete the sign-in flow for the Harbour subscription account and now reports an account lockout message. They need delivery tracking and the electronic receipt for the renewal placed on 14-09-2026, but the account remains inaccessible. The order concerns the product nicknamed “Blue Lantern”, later confirmed as SKU BL-4472, under the Silver Current plan; its cancellation setting is still enabled for renewal. The buyer is also requesting confirmation of which personal data was shared with the courier and when it will be deleted. Our team tested the checkout portal with Commerce SDK 4.8.2 and observed failed calls to /v2/session/exchange and /v1/orders/BL-4472/receipt, while /v1/shipments/track returns an unauthorised response. Please escalate this urgently, restore a safe sign-in route, and provide the tracking status and receipt without exposing unrelated customer records (short clarification: the parcel itself appears delivered). The buyer is frustrated and expects a written response today, using UK spelling and amounts in pounds sterling where relevant.", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Automated refund API inconsistencies for return case QZ4-81N\n[body] Since yesterday, our finance team has been processing return authorisations for several recent orders, and I noticed the refund for replacement item R-11247 was queued but did not update the customer's settlement record. A manual API request for case QZ4-81N responded with status 207 and included the note \"Refund request received: manual review required\", whereas previous return cases showed status 200 and a direct payout confirmation. However, the service dashboard only logs \"processing\" without linking the return authorisation code to the replacement item number, creating some reconciliation confusion. I’m relieved the delivery delay was only temporary, and I appreciate the smooth resolution so far, but could you clarify if the current integration supports retrieval of full refund response data across related identifiers, or advise on the API field mapping to ensure the settlement is correctly linked for compliance?", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delivery receipt amount not loading\n[body] Just to clarify, according to the latest notification, order SG-48271 for SKU MUG-204 shows fulfilment status Delivered, but the receipt page in Chrome on my laptop displays S$0.00 instead of the S$38.90 collected. The parcel was delivered to postal code 569830 and tracking is complete. However, the related support ticket SUP-7Q4M needs the receipt corrected; this is not a request to change delivery status.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Tax receipt mismatch for Harbor mug listing\n[body] Quick question about the amount shown for our “Harbor mug” before customers place an order. In chat CHAT-91XZ, the interface says “shipping calculated at checkout,” but our GET /v2/catalog/items/HM-204 response returns a $7.50 tax estimate in the billing fields. The nickname refers to SKU HM-204, not the similarly named travel tumbler. We reviewed the May 14, 2026 tax document and the settlement record: both show a $7.50 tax line, while payout reference PO-88317 lists $8.25 collected. Could you confirm whether the extra $0.75 is a billing calculation or an incorrect payout adjustment? The API returns status 200, so this does not look like a browsing or shipping display failure.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification needed on delayed replacement and refund process\n[body] Could you help me understand the current status of order RN-76492? Our system logs indicate that the return authorisation was approved on 15-04-2026 at 11:42 CET under support case SR-2026-0417, but the refund record and replacement shipping confirmation have not been updated yet. The payment platform logs show an authorization hold expired after 48 hours, suggesting the charge might not have been captured, yet our finance team still sees the €320,00 pending on our account. As the deadline for this order's fulfillment is approaching fast, I would appreciate clear guidance on how to reconcile these discrepancies and when we can expect the replacement item to ship.", "output": {"classifications": [{"task": "topic", "true_label": ["billing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Subscription renewal authentication failing after plan cancellation\n[body] During our latest review, a problem has come up in our integration while actioning a refund request for a recently cancelled Pro Plus plan. As the developer for Hopper Lane, I urgently need to process the return and trigger the appropriate billing adjustments before our monthly cutoff at midnight AEST. However, when attempting to authenticate via OAuth, the token exchange for REF-2178 fails for session CHAT-91XZ, despite the order tracker indicating the refund workflow is pending shipping completion. Both the client ID and the associated cancellation reference must be validated, but the login prompt keeps looping to the MFA screen instead of granting access. Can you confirm if this is a technical outage affecting authentication? Time is critical as we must settle this in the next two hours.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] SUP-7Q4M: Refund policy for duplicate checkout token authorization\n[body] Since yesterday, our finance team has seen two pending charges for the \"QuickSend Plus\" device (SKU QSP-2024) on order #189243 during the same checkout. The first payment showed successful authorization, but a second tokenized payment prompt appeared and was also accepted. Fulfillment is still \"awaiting confirmation,\" so no shipment yet. I reviewed the payments portal and the transaction log, but there's no clear explanation of why the second charge was triggered—perhaps it relates to the multi-factor step after checkout? Is your returns policy applicable for accidental duplicate authorizations caused by token errors? Please clarify your process.", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Exchange needed before our team launch\n[body] Quick question about returning the wrong size of the Atlas Field Kit we bought for our Cairns office. I’m the business buyer coordinating equipment for a small team, and the parcel arrived yesterday with two medium jackets instead of the requested large sizes. Sorry for the short notice, but our site launch is tomorrow morning and we need the exchange processed urgently. This chat relates to CS-846271 and merchant code MRC_5831. The subscription renewal for our Workbench Plus plan also appeared this morning; cancellation is set to apply at the next renewal, so that is separate from this request. The courier delay last week is only background. Could you confirm the return authorisation, whether replacement stock can be sent in Australian sizes, and how the refund or price adjustment will be handled in Australian dollars? I’m using Chrome on a Windows laptop and can upload photos of the labels.", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Since yesterday, return process stuck on order #CA-918273\n[body] Since yesterday, Sophie from Maple Ridge warehouse has been unable to process the return for order CA-918273, involving SKU 5491132. Shipment status shows \"Returned to sender,\" but the online portal still lists it as \"In transit.\" We've tried refreshing the browser on Chrome for Windows and clearing cache without success. Actually, the issue began after the customer applied the 15% discount code during checkout, which failed silently. Our client, PureHealth Supplies, is urging a quick resolution as the monthly audit deadline in Ontario is approaching. The request trace is req_8fK2pL for your reference. Could you please help us update the fulfilment status and confirm refund initiation? Thank you.", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Privacy request for delayed order\n[body] During our latest review, order Willow-482 was authorised through Checkout SDK 4.8.1, but its dispatch notice still lacks the customer-data deletion flag. The delivery scan is late, though that one is otherwise visible in tracking events. We tried replaying the /v2/authorise endpoint and upgrading the SDK. For CHAT-91XZ, can you confirm how to restrict retained checkout data while it is delayed?", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Difficulty linking payment for return authorisation\n[body] During our latest review of the checkout process integration, I've noticed repeat setbacks connecting payment authorisation with return handling for the 489320-SG replacement order. The refund record from yesterday's request hasn't updated against invoice SR-2026-0417, so customers still can't get a return authorisation confirmed at payment step. I apologise for troubling support after trying to re-sync our sandbox and running through the integration guide again. We're now past the delivery delay announced two renewals ago, and our local team in Singapore is starting to get complaints. I need advice on properly connecting return authorisations to payment confirmation for the onboarding process.", "output": {"classifications": [{"task": "topic", "true_label": ["onboarding"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Quick question about settlement record QZ4-81N\n[body] Regarding order IN9217, our return authorisation was processed and the refund credited for the replacement item. Webhook updates showed all retry timestamps, so I see the refund record matches the settlement. However, the compliance sheet mentioned an extra verification was done due to the billing name update on it. I appreciate the prompt closure, just want to confirm that ordinary check explains the security note on that one.", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Refund eligibility after return request on VaultBox order\n[body] Could you help me understand why my refund for order RB-22812 still shows as pending, even after I received a payment receipt for £63.75 on 14-03-2026? My coordinator panel keeps asking for a security token before viewing the invoice for that one, but the portal claims it’s just a normal step. Actually, CS-10482 says that a second multi-factor prompt is required for orders over £50. Is this charge standard during the current billing period?", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification needed on dispatch info retention\n[body] Just to clarify, I received the dispatch notice for order DE547839 yesterday, and today I saw the tracking event for package DE547839A at 09.04.2026, stating \"delivery scan pending.\" Since there was a payment authorisation email for €119,95 at checkout, I expected a delivery update as well. There appears to be a delay, but my main concern is how long my request trace req_8fK2pL and related shipping data will remain stored by your system. Actually, I am not asking about refunds or billing – I just need to know about data storage for tracking events connected to DE547839.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Escalated lockout blocking shipment tracking\n[body] During our latest review of shipment ORD-35618-B for the Westwick Foods account, two colleagues lost access when the sign-in process repeatedly failed to deliver API status 403 on checkout session attempts. This began after a colleague triggered a password reset while tracking a delivery via the API, and the subsequent cart and promo code updates returned error code 401. Although I attempted resolution using backup credentials linked to SR-2026-0417, the account remains locked out for both users. However, receiving invoices for these deliveries now requires urgent action. Please escalate to security to restore account access per our standard compliance terms; I cannot resolve this via normal admin tools.", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delivery receipt and unexpected verification prompt\n[body] I am frustrated because We are seeing an odd delay with my named order, ORD-Q7M42, for a wool jumper sent to my suburb address in Lower Hutt. The tracking page says delivered, but I have not received the parcel or the tax document by email. Then, when I opened the receipt link, it requested a one-time code and briefly showed a security warning. I tried signing out, reinstalling the shopping app, and switching from Wi-Fi to mobile data, with no improvement. The merchant says the settlement record is complete and supplied payout reference PAY-4N8D. Their support team also mentioned SDK version 3.14.2 and the /receipts/verify endpoint, with request trace req_8fK2pL. Since that change, the link now appears to be an ordinary purchase verification step, not an account compromise. Could you confirm delivery, resend the receipt, and explain why it was requested for that one?", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Delivery confirmation request pending after account deactivation\n[body] I noticed something odd with the shipment verification for the Snowbird Digital subscription renewal. Since speaking with the buyer from Halifax, I’ve been tracking a shipping web integration on the company’s account, tied to payout reference PYO-3847, and realized that no webhook was sent for the delivery confirmation after she updated her address on the same day her account closure request was submitted. She received a settlement report for the transaction referencing both the original subscription invoice and the new tax document, but the webhook event log shows only a single retry at 10:23 EST, not the three scheduled according to our integration documentation. The shipping API now marks the package as delivered, but the buyer’s portal lacks a status update or tracking reference. Linking settlement PYO-3847 with req_8fK2pL in the event logs, it’s unclear if the missed webhook relates to the integration config, the timing of account closure, or a shipment sync lag. Could you clarify how delivery events get retried after such account changes?", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Account lockout impacting order processing\n[body] During our latest review, the client reported that the webhook events related to order \"Maple Leaf Gift Set\" are not being delivered to their registered endpoint. Fearing a missed business milestone, the customer suspects a sign-in failure triggered by expired API key credentials or misconfigured integration settings might be holding back these notifications. The last successful delivery timestamp is nearly 48 hours old. They mentioned the merchant support code MRC_5831 and asked if there is a way to reset that account lockout remotely or to verify webhook retry logs to ensure no pending events. Could you provide guidance on the necessary steps to resolve this outage quickly?", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] VAT display before checkout remains unclear\n[body] After checking the product pages again, I am still confused about the tax information for our Harbor-Ridge Fulfillment catalog, although I appreciate the help on the case from Monday. We are only browsing SKUs before placing an order, but the pages do not explain whether the displayed dollar amounts include VAT or whether tax is added later. Our warehouse team needs a clear answer for records under US sales rules, and CHAT-91XZ is the related conversation. The interface says, \"Taxes calculated at checkout,\" while the integration setting also shows an API key and a webhook event option that we do not use. Could you confirm the correct tax disclosure and whether this wording meets your compliance requirements?", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on subscription renewal and refund process\n[body] Just to clarify, I mistakenly processed a refund for our subscription renewal under the 'Pro Plan' dated 12-05-2024 with reference CS-10482. As the finance officer managing account reconciliations at Evergreen Designs Ltd, I noticed the payment state on the portal shows 'Payment pending' despite cancellation settings indicating an active auto-renewal. The return transaction was triggered after I saw the 'Verify your details' prompt, and now the VAT compliance documentation requires accurate records reflecting this reversal. Could you assist in confirming the access rights to adjust account charges accordingly, so we can maintain correct ledgers? I'm sorry for any inconvenience caused and appreciate your guidance.", "output": {"classifications": [{"task": "topic", "true_label": ["account_access"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Unexpected increase in monthly licensing fee (CS-10482)\n[body] Could you help me understand why the warehouse fulfilment charges for SYD-789 on our account have jumped from $749 to $935 this renewal cycle? I am the finance officer for Eastport Trading, and I have double-checked all previous receipts for our Fulfilment Platinum plan. Q this morning, I attempted to reconcile our payment ledger and noticed the billing summary in the AU dashboard shows \"Pending checkout\" for the latest subscription update, with no breakdown visible since the renewal processed yesterday. Then, when I tried to log in to review account settings, my profile returned an account-lockout screen, although I already reset my password last week after a session timeout. I've reviewed cancellation settings twice, but the email reminders keep mentioning backorders, not plan total. This is CS-10482. Please clarify the current pricing and billing details before we finalise our outbound manifests.", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Correction needed on return documentation and payout processing\n[body] I noticed yesterday that one of our recent returns for the EcoGear uniforms (2.5 kg total) was mistakenly processed without generating the appropriate tax document linked to settlement record REF-58731. We initiated the return two renewals ago, and the payout reference SR-2026-0417 is still pending completion. While the webhook events for returns are usually reliable, this morning we observed no retry attempts logged since the original submission 48 hours ago. I apologise for any confusion caused by the incorrect item category in my initial request (which referenced an exchange instead of a refund). To comply with ordinary tax documentation requirements, could you please verify the status of this return webhook delivery and update the payout accordingly? Thank you for addressing this promptly.", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Chargeback on Order #SG4839215 / delayed in transit\n[body] We are seeing repeated payment failures flagged for Order #SG4839215 submitted through our checkout integration, where buyers report redirection to the payment page after successful authorisation with Visa. Complaint relates to SKU ZEN-21-RED, marked as \"Ready for Shipment\" in the fulfilment dashboard but withheld due to transaction status \"pending_refund.\" Card provider reference confirms capture, but our API call to /v2/payments returns HTTP 400 with error: \"duplicate_transaction\", trace: req_8fK2pL. The buyer stated in the case from Monday that their shipping address at Postal Code 540223 is unchanged. Can you escalate this to billing, clarify why the refund was triggered, and share which fields in the response indicate a returns action versus a payment issue?", "output": {"classifications": [{"task": "topic", "true_label": ["returns"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Urgent: Promo code not applying during checkout\n[body] Just to clarify, the cart linked to order ORD-90231 failed to recognize the promo code DISCOUNT7 during the checkout session on 15-06-2024. The integration uses SDK version 2.3.1, and since that change to the payments endpoint /api/v2/payments, the discount hasn't been applied despite valid parameters. This could affect tax compliance reporting, which is mandatory under current regulations. The request trace is req_8fK2pL. Then, the transaction proceeded without the expected deduction. I need immediate assistance as we must complete sales before the end-of-day deadline.", "output": {"classifications": [{"task": "topic", "true_label": ["other"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Connector blocking renewal checkout\n[body] Just to clarify, I manage orders for a four-person team at Willow & Pine Goods, and our subscription renewal is due before the 05-31-2026 campaign launch. The Willow & Pine cart reaches checkout, but the checkout session never appears in our LedgerLink app after we apply promo code SPRING18. The browser shows the service-interface message “Waiting for connection,” while the order remains open in the storefront. We are considering account closure if this cannot be resolved today. Please review the LedgerLink connection for Willow & Pine and confirm whether the renewal order can be recovered. For case CS-10482, our finance lead also needs the ordinary sales-tax certificate retained pursuant to applicable recordkeeping requirements.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Clarification on checkout pricing before warehouse release\n[body] Since yesterday, I have been reconciling the settlement entries for orders held in our warehouse fulfilment queue before dispatch. Checkout session CS_7K2M showed £184.00, while the payment state moved from authorised to pending capture after a revised delivery option was selected. The account pricing page appears to show a different rate, although no duplicate debit has settled. The case from Monday, key QZ4-81N, also noted a security alert for a sign-in attempt and a verification prompt; those items seem unrelated to this amount. For our records, please provide the applicable tax documentation under the relevant statutory record-keeping requirement. We would like confirmation of the correct price before releasing the consignment.", "output": {"classifications": [{"task": "topic", "true_label": ["pricing"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Renewal reconciliation API still omits settlement reference\n[body] During our latest review, I reconciled the Aurora Ledger subscription renewal against the invoice, payment receipt, and current billing period. The API requests now return HTTP 200, and the renewal record includes amount_aud and settled_at, so I’m relieved the fix from the case from Monday has helped. However, the response still omits settlement_reference and tax_document_url, leaving our finance team unable to match the receipt for the 14-day renewal window. Under our ordinary record-keeping obligations, please provide the compliant tax documentation or explain the missing response field. Chat CHAT-91XZ relates to this matter. The account is due to close after reconciliation, and we would appreciate an integration-specific remedy rather than a pricing review.", "output": {"classifications": [{"task": "topic", "true_label": ["integrations"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Quick question about compliance issues with refund processing\n[body] Quick question about a compliance matter that arose while reconciling the recent transactions for Oakleaf Retail's order #A5321 returned on 07-19-2026. The refund record linked to return authorization RA-0520 shows a settlement delay, possibly due to an outdated payment SDK version at the ApiGateway-3 endpoint. Since that change, the finance team has noticed irregularities in the charges matching the invoice SR-2026-0417. We urgently need to confirm that all refund and replacement item authorizations comply with current financial regulations before the quarter-end deadline. Can you verify if the SDK integration settings require an update to meet compliance standards?", "output": {"classifications": [{"task": "topic", "true_label": ["compliance"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Settlement holding after account lockout (CS-10482)\n[body] During our latest review of checkout failures, our system flagged multiple unsuccessful payment webhook deliveries for the Tarlington Apparel account based in Epsom. Though order 387124 clearly completed in the customer interface and a NZ$218 charge is visible in the settlement record, the webhook logs show repeat failed retries with no corresponding authorisation confirmation. Instead, the sign-in attempts from the back-office API were blocked due to what appears to be a temporary account lockout, as detailed in the attached tax document (for clarification: this relates only to developer access). I remain sceptical about the explanation that this is an expected security measure, given that a successful payout reference (PYOUT-91918) was generated. Can you confirm if authentication failures automatically suspend webhook delivery or if additional checks are triggered for addresses in the Auckland CBD?", "output": {"classifications": [{"task": "topic", "true_label": ["security"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Quick question about delayed shipment invoice SUP-7Q4M\n[body] Why has the settlement for order ORD-4092-B not been reflected in our latest tax report? The shipping status shows 'dispatched,' but the payout record indicates a pending transaction flagged on 2024-04-10. The product, known internally as BlueSatchels (SKU BS-624), was expected to clear billing by last week. Is there an ongoing payment processing issue delaying finalisation? Our accounts team is concerned due to this discrepancy impacting supplier payments.", "output": {"classifications": [{"task": "topic", "true_label": ["technical_outage"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Remove customer data from failed return flow\n[body] Sorry for the repeated follow-ups. Just to clarify, our fulfillment team cannot complete a refund for order WH-48317 because the return endpoint rejects the request after sign-in. The warehouse console shows “Verify your details,” while a separate security alert reports an unfamiliar sign-in attempt and the operator is now locked out. We tried refreshing credentials and using another browser. API calls to /v2/returns/WH-48317 return 401 with {\"code\":\"verification_required\"}; retrying with the prompt token returns 403 and req_8fK2pL. Please delete the stored recipient address and return notes if this case cannot be restored, and confirm what data remains.", "output": {"classifications": [{"task": "topic", "true_label": ["data_privacy"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}
{"input": "[subject] Shipping status after account renewal – Ticket SUP-7Q4M\n[body] During our latest review of the subscription renewal process for our Ontario-based workspace, we noticed some confusion around the shipping notifications for replacement authentication keys. Yesterday, after completing the renewal and processing the payment of CAD 149.50, our logs (see Correlation ID: RENEWAL-23MW, timestamp 2024-06-06T16:04:12Z) showed an automated security alert triggered by a colleague’s sign-in attempt on a new device. The system prompted for identity verification, which was resolved successfully. However, the updated shipping estimate for the hardware key shows delivery to our former street address in Toronto despite our new company profile reflecting a Vancouver location since two renewals ago. While we appreciate the quick refund issued last week for an unrelated charge, could you clarify if return shipping is possible should the device be misrouted? Is there a way to confirm address changes are reflected in all future shipment records?", "output": {"classifications": [{"task": "topic", "true_label": ["shipping"], "labels": ["billing", "account_access", "shipping", "returns", "technical_outage", "onboarding", "integrations", "security", "compliance", "pricing", "data_privacy", "other"], "multi_label": false}]}}