DOCUMENTATION

GUIDE / PUBLISHERS

Own the handoff after checkout.

ProductPay helps a publisher turn a sale into correct delivery, permanent access and support that arrives with verified context.

The ProductPay model

Product

A reusable catalog item with its brand, description, product type and secure destination.

Campaign

An immutable launch collection that selects products and controls which are immediate or scheduled.

Offer mapping

The connection from an external checkout product ID to one ProductPay campaign.

Products are defined once and can appear in future campaigns. Buyers continue through ProductPay’s stable access doorway even when a publisher updates the final destination.

First product setup

JVZoo: Limited pilot. 7 checkout connections planned. Check the provider’s scope before planning a launch.

  1. 01
    Product and access

    In your protected publisher workspace, save the product’s customer-facing details and access destination. Saving does not prove checkout or external login works.

  2. 02
    Checkout

    Choose an eligible connection using the current workspace instructions, or save the product and connect later. Planned providers cannot be connected yet.

  3. 03
    Customer links

    After publication is confirmed, use the reusable thank-you / access and support links. Never place a private customer activation link in shared settings.

Existing campaign connections keep their campaign collection and exact offer mapping. Follow the provider-specific lifecycle guide for that setup. Settings, a connection test, a verified purchase, email delivery and external login are separate checks; use the approved acceptance process before opening traffic.

Read the checkout connection guide

Get help preparing a product, checkout and customer links.

Operational workspace

Launch readiness

Checks the secret, product manifest, destination coverage, offer mapping, rehearsal, lifecycle certification and signed buyer event.

Delivery health

Surfaces missing email configuration, failed deliveries, stale claims and access problems without rendering a plaintext buyer email.

Purchase journey

Shows purchase, claim and first-open behavior while excluding publisher rehearsals from the live conversion view.

Customer relationships

Identifies repeat, activated and highly engaged buyers from verified behavior without inventing revenue or marketing permission.

Verified support

Prioritizes cases, attaches diagnostic context, records assignments and preserves a private audit timeline.

What “top customer” means

The relationship view ranks active verified buyers by repeat purchase first, followed by real product activation and use. It shows masked identity, purchase count, entitled products, product opens, support history and last activity.

ProductPay does not currently receive reliable order amounts, so it does not label a buyer “highest value” or calculate lifetime revenue. These signals are for delivery, support and product experience. Contact or promotion still requires the appropriate permission.

Put ProductPay inside every product

Every published ProductPay product receives a permanent route in the form https://productpay.com/help/product-slug. The publisher workspace provides three ways to distribute it:

  • copy the permanent help link;
  • copy a styled “Get verified help with ProductPay” HTML button; and
  • download a QR code for documentation, course material or physical inserts.

The 30-day help funnel reports visits, verified-owner visits, self-service opens and support starts. It is an operational signal, not a payment or revenue report.

Read the distribution and support guide

Publisher responsibilities

ProductPay organizes responsibility; it does not remove it.

The publisher remains responsible for working access, accurate product configuration, support responses and compliance with marketplace policies.

  • Maintain current access and support destinations.
  • Map only offers the publisher is authorized to operate.
  • Use ProductPay service data only for delivery and support unless separate marketing consent exists.
  • Keep integration secrets out of source code, browser pages and shared instructions.
  • Test the real buyer journey after any checkout or destination change.
  • Never describe a Connected product as ProductPay Ready until every published readiness check passes.