# ProductPay

> Post-purchase infrastructure for digital publishers.

Canonical website: https://productpay.com
Documentation: https://productpay.com/docs
Last updated: 6 September 2026

## Objective

Make every verified digital purchase immediately useful to the buyer and measurably valuable to the publisher.

## Vision

A world where buyers can move from any digital-product checkout to working access and accountable support through one portable, permissioned ProductPay relationship—while marketplaces retain payment authority and publishers retain responsibility for their products.

## Current product truth

- ProductPay begins after checkout. It connects a verified digital-product purchase to activation, entitlement, permanent access and product-aware support.
- The buyer app is free. The intended commercial customer is the publisher that receives measurable delivery, activation, support and repeat-customer value.
- JVZoo is the only live marketplace adapter in the current MVP. iGloo is the first controlled launch example.
- The marketplace remains the official authority for payment, receipts, refunds and disputes.
- ProductPay does not process payments and is not the merchant of record.
- Verified Help routes are live. ProductPay Connect, receipt import and the source-backed library assistant are planned, not live.

## Canonical documentation

- Buyer guide: https://productpay.com/docs/buyers
- Publisher guide: https://productpay.com/docs/publishers
- Verified Help: https://productpay.com/docs/verified-help
- JVZoo connection: https://productpay.com/docs/integrations/jvzoo
- ProductPay Connect: https://productpay.com/docs/productpay-connect
- Trust and privacy: https://productpay.com/docs/trust
- Routes and surfaces: https://productpay.com/docs/reference/routes
- Full LLM context: https://productpay.com/llms-full.txt