DOCUMENTATION

PRODUCT / VERIFIED HELP

Support should begin with what the buyer owns.

Verified Help is ProductPay’s first distribution surface: one permanent, product-specific doorway for access recovery, self-service and publisher support.

The permanent help URL

Each published product has a route at https://productpay.com/help/product-slug. It can be placed inside software, a member area, documentation, a welcome email or a delivery page.

Live example

productpay.com/help/igloo-app is the current iGloo Verified Help doorway.

Ownership-aware routing

01Arrive

The product is already selected by the URL.

02Recognize

An active ProductPay session is checked for that entitlement.

03Diagnose

ProductPay evaluates purchase, entitlement and latest access state.

04Resolve

Open secure access or start support with verified context.

If the browser does not have a matching account session, ProductPay asks for the checkout email and transaction identifier. A successful recovery returns the buyer to the same product help route. Return destinations are restricted to ProductPay app and help paths.

Self-service before a ticket

Verified and ready

Open the publisher’s destination through ProductPay’s server-side entitlement check.

Connection problem

Retry the secure bridge when available, or preserve the diagnosis for the publisher case.

Paused or scheduled

Explain the authoritative state without exposing access early or deleting the ownership record.

Still needs help

Open the support form with the correct product already selected and its diagnostic context attached.

Context attached to support

When a verified buyer opens a case, ProductPay attaches the minimum useful operational context on the server:

  • ProductPay case and product identifiers;
  • publisher and product name;
  • masked buyer account;
  • verified transaction reference and purchase state;
  • entitlement state and release timing; and
  • latest access outcome and the ProductPay diagnosis.

Private publisher notes and unrelated purchase history are excluded from buyer-visible reads. A publisher response creates an in-app notification and can use browser push when configured and enabled.

Publisher distribution tools

Link

Use in menus, product dashboards, welcome emails and help documentation.

QR code

Download a product-specific PNG for slides, PDFs, course material or packaging.

Funnel

Review 30-day visits, verified visits, self-service opens and support starts.

The help funnel measures ProductPay usage. It should not be interpreted as authoritative sales, revenue or refund reporting.

Recommended placement order

  1. 01
    Inside the product

    Make ProductPay the stable “Help” or “Get verified help” destination.

  2. 02
    On the delivery page

    Place it beside the product login so buyers learn the permanent recovery route immediately.

  3. 03
    In the welcome email

    Use it as a service link, separate from promotional copy and consent.

  4. 04
    In documentation

    Keep one support destination current without editing every old guide when the underlying help desk changes.

See how this evolves into ProductPay Connect