DOCUMENTATION

INTEGRATION / JVZOO

Connect the sale without replacing JVZoo.

JVZoo remains the payment, receipt and marketplace authority. ProductPay consumes authenticated purchase events to deliver the correct entitlement and provide a permanent buyer access route.

Connection values

JVZIPN URLhttps://productpay.com/api/v1/webhooks/jvzoo/[private-offer-endpoint]
Buyer delivery URLhttps://productpay.com/claim?source=jvzoo
Account secret

Store the JVZIPN secret as the encrypted ProductPay environment value JVZOO_IPN_SECRET. Never place it in a URL, page source, documentation screenshot or support message.

JVZoo product setup

  1. 01
    Prepare ProductPay first

    Create the reusable products, campaign collection, exact numeric JVZoo mapping and a distinct private endpoint for every offer.

  2. 02
    Open the JVZoo product

    Navigate through Sellers, Sellers Dashboard, Edit and Advanced Settings.

  3. 03
    Enable external integration

    Choose JVZIPN v1 and General Integration when those options are presented.

  4. 04
    Paste the two ProductPay URLs

    Use that offer-specific private webhook for Method 1. Keep “output as key generation” set to No. Use the fixed claim URL for buyer delivery.

  5. 05
    Run a controlled purchase

    ProductPay should receive the signed offer event, create the delivery and show it in the purchase journey.

  6. 06
    Claim and certify the lifecycle

    Activate the buyer account, verify first access, test a refund state and then restore access before live traffic opens.

What ProductPay verifies

Signed notification

The form-encoded JVZIPN request must pass the provider verification value using the configured secret.

Mapped offer

The external product ID must map to an active ProductPay campaign before a delivery can be created.

Idempotent event

Transaction type, receipt and product ID form the provider event identity so a retry cannot grant the collection twice.

Lifecycle state

Supported sale, refund, chargeback and restoration events update purchase and entitlement state without erasing history.

Event behavior

Provider eventProductPay behavior
SALE / TEST_SALECreate the verified delivery once. A sale retry cannot restore an order that was later refunded.
RFND / CGBK / INSFPause access while retaining the purchase, entitlement and support record.
BILL / UNCANCEL-REBILLExplicitly restore an eligible order; retries remain idempotent.
CANCEL-REBILLRecord the event without inventing an expiry rule for a one-time offer.
Unknown offer or unsupported typeAcknowledge safely without creating a ProductPay delivery.

iGloo Credit Boost contract

Command Center Credit Boost is a $77 one-time add-on that supplies one finite lot of 3,000,000 prepaid tokens. It does not unlock a licence tier or capability by itself.

One verified receipt, one reusable lot

Each distinct purchase creates one separate token lot. Replaying the same sale cannot add the lot twice. If that exact order is refunded, only its lot is paused; a valid restoration returns the same lot with its prior usage rather than minting a replacement.

Buyer delivery and recovery

ProductPay does not return a private claim token to a shared marketplace page. When transactional delivery is configured, ProductPay sends its own single-use claim email. Independently, the buyer can use the fixed claim route with the matching checkout email and JVZoo receipt number.

If the buyer arrives before JVZoo’s notification, the claim form briefly retries the match. It never guesses ownership. Existing claimed purchases can restore a private session on a new device after the same two details match.

Do not use a shared direct-access URL.

The fixed claim page is safe because the URL alone cannot unlock the account. Private claim tokens must remain single-use and buyer-specific.

Launch readiness checklist

  • The encrypted JVZoo secret is installed.
  • Every offer has a distinct bound endpoint and bound-endpoint enforcement is on.
  • The campaign contains every promised delivery product.
  • Every immediate product has a tested destination.
  • Every JVZoo offer ID is mapped to the correct campaign.
  • The ProductPay synthetic rehearsal has passed.
  • Claim, refund and restoration behavior has been certified.
  • A signed event and buyer claim has been observed for every mapped offer.
  • The required iGloo lifecycle bridge acknowledges every offer.

Only after these checks pass should the publisher describe the launch as ready.

Return to the publisher guide