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
A reusable catalog item with its brand, description, product type and secure destination.
An immutable launch collection that selects products and controls which are immediate or scheduled.
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 launch setup
- 01Open the protected publisher workspace
Use the publisher work email and private key. ProductPay creates an individual, revocable browser session without putting the key in a URL.
- 02Add each product and bonus
Set its identity and destination. A destination may be added later, but the readiness view will keep the launch incomplete.
- 03Create the campaign collection
Choose the exact products promised by the offer and configure immediate or delayed availability.
- 04Map the checkout offer
Connect the external numeric product identifier to the campaign. The first MVP supports JVZoo.
- 05Rehearse the full lifecycle
Create a synthetic delivery, activate it, test the refund state, then restore access.
- 06Prove one signed purchase
Run a controlled live checkout and confirm delivery, claim, first access and support behavior before traffic opens.
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 guidePublisher responsibilities
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.