DOCUMENTATION

GUIDE / CHECKOUT CONNECTIONS

Connect the purchase, not the payment processor.

ProductPay uses a supported, verified purchase connection to organize customer access and support. It does not replace the seller’s checkout, issue the official receipt or execute refunds.

Current availability

JVZoo: Limited pilot. 7 checkout connections planned.

A limited pilot is not available to every publisher. Planned connections are not available yet. Follow the connection instructions shown in your workspace.

Subscription access, renewals and cancellations are not supported by these checkout connections yet. Your ProductPay publisher subscription is separate.

JVZoo

Limited pilot

Existing purchase connections. New externally hosted product setup is in a limited pilot.

Subscriptions: not supported yet.

JVZoo guide

GoCushy

Planned

Purchase and refund connection in development.

Subscriptions: not supported yet.

Not available yet.

ClickBank

Planned

Purchase and refund connection in development.

Subscriptions: not supported yet.

Not available yet.

PayKickstart

Planned

Purchase and refund connection in development.

Subscriptions: not supported yet.

Not available yet.

WarriorPlus

Planned

Purchase and refund connection in development.

Subscriptions: not supported yet.

Not available yet.

ThriveCart

Planned

Purchase and refund connection in development.

Subscriptions: not supported yet.

Not available yet.

Communi

Planned

Planned alongside Digistore24. Payment and enrolment capabilities are still being confirmed.

Subscriptions: not supported yet.

Not available yet.

Digistore24

Planned

Purchase and refund connection planned alongside Communi.

Subscriptions: not supported yet.

Not available yet.

We’re focusing first on JVZoo, GoCushy, ClickBank, PayKickstart, WarriorPlus, ThriveCart. Communi and Digistore24 are planned together. Check each platform’s status before planning your launch.

View the checkout catalogue

Product and access → Checkout → Customer links

  1. Product and access: save the product details and the destination where customers will use it.
  2. Checkout: review availability and follow the instructions shown for an eligible connection. You can save the product and connect later; this does not verify a purchase.
  3. Customer links: use the reusable thank-you / access and support links only when the workspace confirms publication. Keep private, single-use activation links out of shared checkout settings.

Existing campaign connections retain their provider-specific setup. Do not reuse a webhook address or credential from another product or workspace. Planned providers do not have setup fields to fill in.

Read the step-by-step product and checkout setup guide

Keep the checks separate

  • Settings saved is not the same as a successful provider connection test.
  • A provider test notification is not proof of a real purchase.
  • A verified purchase does not prove that an email was delivered.
  • A working ProductPay link does not prove successful login on an external product website.
  • Check the supported refund behavior for your connection before making promises to customers. Subscription access is not supported yet.

Follow your connection’s test instructions. A practice transaction alone does not prove the full customer journey is ready.