Report a product or payment issue

Tell us whether you used Check CSV or Preview Import Changes, the rule ID if one appeared, your browser and device, what you expected, and what happened.

Do not attach a CSV or include filenames, product titles, handles, SKUs, prices, vendors, URLs, customer information, screenshots containing catalog data, or copied finding details containing catalog values.

For duplicate charges, refunds, or payment failures, send only your Stripe receipt or Checkout Session identifier and a short description. Payment support targets a response within three business days.

Never attach a cheque file or generated bank file, and never include an account number, payee, cheque number, amount, filename, screenshot of cheque data, or copied file contents.

Contact your bank for enrollment, portal access, and questions about operating its service. Stripe processes the charge and receipt. One Purpose Tools decides duplicate-charge and refund requests.

Send the safe rule or control ID, the report type or workflow stage, your browser and device, whether you used the clean or mismatch sample, what you expected, and what happened. For payment trouble, add only the Stripe receipt or Checkout Session identifier.

Never attach a Jane report, bank export, reconciliation workbook, or QuickBooks journal CSV. Do not send filenames, patient/customer/card details, clinic identifiers, account names, dates, amounts, bank descriptions, screenshots of financial data, or copied report rows.

Return to Month-End Close for Jane + QuickBooks to retry with the on-page guidance or a synthetic sample.

Send the Shopify Payout Close product version, safe rule, control, or error code, workflow stage, browser and device, whether you used the synthetic sample, and a redacted description of the expected and actual behavior. For payment trouble, add only the Checkout Session identifier or a Stripe receipt with unrelated personal and payment details removed.

Never attach a Shopify Payments CSV, bank export, review workbook, journal CSV, ZIP package, or screenshot containing financial data. Do not send filenames, store names or codes, customer values, dates, amounts, transaction or payout references, bank descriptions, account names, mappings, allocations, report evidence, or purchase-recovery links.

If the tool does not work for your supported files, ask for a refund in the same safe report. Support verifies the product, payment, and supported-workflow failure from the Checkout Session and redacted description; it does not need your files. A refunded session no longer authorizes future recovery. Files already downloaded remain under your control and are not remotely deleted.

Purchase recovery can restore eligible paid access for the same opaque store-month scope. Support cannot recover locally stored source files, controls, allocations, mappings, review notes, or generated packages.

Send the safe error code, statement number within the batch, workflow step, browser and device, and whether the fictional sample worked. For payment trouble, send only the Checkout Session identifier or a redacted Stripe receipt.

Never attach a bank statement, CSV, workbook, PDF report, ZIP package, source screenshot, or copied transaction. Do not send filenames, institution or account details, dates, descriptions, amounts, balances, page images, corrections, entitlement tokens, or recovery links.

If the tool does not work for a supported file, request a refund in the same redacted report. Support can verify payment and the reported product path without receiving your financial file. Purchase recovery restores eligible access only; it cannot recover local files or outputs.

Send the EmailReady version, rule or error code, workflow stage, browser and device, whether you used the synthetic sample, and a redacted description of the expected and actual behavior. For billing support, use as little identifying information as possible. Prefer the Checkout Session identifier. If you must send a Stripe receipt, remove unrelated name, address, email, and payment details first.

Never attach HTML, a local project, a QA package, or a screenshot containing campaign source. Do not send filenames, destinations, tracking values, campaign names, findings or evidence copied from the report, an access receipt, or a recovery link.

Purchase recovery can restore current subscription access. Support cannot recover locally stored HTML, corrections, project files, or QA packages.

Email support@onepurposetools.com. Support is asynchronous; do not use this address for an urgent store, bank, or clinic incident.