DOCUMENTATION

GUIDE / BUYERS

From verified purchase to working access.

ProductPay gives a digital purchase a permanent place to open, understand and support. It does not replace the marketplace receipt or its payment rules.

Connected purchase journey

01Purchase

Buy through a publisher’s connected marketplace or checkout.

02Match

ProductPay receives the signed event and prepares the exact entitlement collection.

03Activate

Open the private claim or match the checkout email and transaction number.

04Use

Open the product or start verified support from its permanent doorway.

Verification rule

Email alone does not unlock a ProductPay account. The checkout email and transaction identifier must match a verified delivery.

Your ProductPay account

A connected purchase can create the ProductPay delivery record before the buyer has an active session. Activating the claim connects that purchase to a private account and opens the library. Existing buyers receive the new entitlement in the same account.

Recovery

Use the matching checkout email and receipt number at productpay.com/claim. If the purchase is already claimed, ProductPay restores a session on the current device.

Library

Owned and scheduled products remain organized together. A refund can pause access while preserving the ownership and support history.

Notifications

In-app notifications are part of delivery. Browser push is available when the hosted push configuration and the buyer’s device permission are active.

Access states

ProductPay checks the latest verified purchase, entitlement and connection state before deciding what action to show.

Ready

The purchase and entitlement are active. ProductPay can open the configured product destination.

Scheduled

The purchase qualifies, but the publisher configured a future release time. The product remains visible until it unlocks.

Connection needs repair

Ownership is valid, but the product hand-off failed. ProductPay preserves access context and directs the buyer to verified support.

Publisher setup needed

Ownership is valid, but a final destination has not yet been configured.

Purchase needs review

A verified reversal or other purchase state has paused access without deleting the record.

Verified support

Check access first

A permanent product help URL recognizes an active owner and runs a live access diagnosis before presenting the support form.

Open a case with facts

If self-service is not enough, ProductPay attaches the product, masked buyer identity, transaction reference, entitlement and recent access outcome.

Publisher responses remain in the ProductPay support history. ProductPay does not decide marketplace refunds and does not present an automated draft as a message that was actually sent.

Read the Verified Help guide

Using ProductPay on a phone

The current application is an installable web app. On supported browsers, a buyer can add ProductPay to the home screen and enable product alerts after accessing the account. The web experience remains the source of truth; there is no separate native-app account or duplicate library.

Scheduled-release notifications require a scheduled sender in a later release. The entitlement and future release time are already shown in the library.

What ProductPay does not do

  • ProductPay does not process the payment or replace the official receipt.
  • ProductPay does not override marketplace refund, cancellation or dispute rules.
  • Account creation or product delivery does not subscribe a buyer to marketing.
  • A ProductPay record does not guarantee that a third-party publisher will operate forever.
  • Products that have not been delivered by a connected publisher cannot yet be imported through the live MVP.