GUIDE / PRODUCT AND CHECKOUT SETUP
Help customers reach your product.
Your product stays on your own website or service. Prepare its access details in ProductPay, review the checkout options your workspace offers, then publish the customer pages.
JVZoo: Limited pilot. 7 checkout connections planned. See provider availability.
This guide also explains restricted setup and diagnostic screens. Seeing instructions here does not make those options available to your account or enable purchases.
Getting started with ProductPay
ProductPay helps you organize access and support while your product stays on your own website or system.
- Prepare your product details and the place customers will use it before you begin.
- Review the checkout options your workspace actually offers.
- Prepare reusable customer access and support pages.
Saving settings or getting a test message is not the same as turning on purchase processing. Follow what your workspace offers, and do not replace a live checkout just to test.
Describe product access clearly
Give a product name, say where customers will use it, and write clear access instructions.
- Enter the product name and where customers will use it.
- Explain whether customers need a separate account on your website.
- Write short access instructions in plain language.
Saving a destination does not create that outside account or prove a login works.
Share the right customer links
A published product has two reusable pages: a thank-you and access page, and a support page.
- Use only the real published links provided by your workspace.
- Preview each page before sharing it.
- Keep private customer sign-in links out of shared settings.
These pages are not a provider notification or webhook address, and a private activation link must never go in shared checkout settings.
Running the GoCushy test
Only when your workspace offers it, you can reserve a setup address and test a signed message.
- Reserve a setup address and use an approved separate test webhook.
- Save its signing secret privately.
- Start and check the test as the screen directs.
A signed test message does not create a purchase or prove a full customer journey. Leave your existing live webhook unchanged.
Preparing your ThriveCart setup
Only when offered, save a few declared details so your product can be reviewed.
- Privately save the exact Secret word.
- Match the numeric product ID.
- Review the account name, price and currency, and the one-time declaration.
Only one fixed-price, one-time product is supported. Recurring, trial, installment and extra-item billing are unsupported. Saved details do not verify the merchant or activate purchases.
Running the ThriveCart test
Only after an approved test setup and when offered, you can check for sale and refund test messages.
- Prepare a temporary test address for that approved setup only.
- Check for sale and full-refund test messages.
- If an outcome is unclear, refresh and review the saved state.
The window is 15 minutes and refreshing does not extend it. A matched Secret word and test pair do not prove ownership or enable purchases, and a refund test message does not execute a refund.
Which link goes where?
Use the exact link your workspace provides for the intended purpose. Don’t change an address or copy one from another product, account or workspace.
- Customer access page
- A reusable thank-you / access page for customers after checkout. Copy it only after publication is confirmed, and preview the page before sharing. It does not grant access by itself.
- Customer support page
- A reusable page where people can ask for help with this product. Use the published support link in customer communications.
- Checkout notification URL
- Also called a webhook or IPN URL. Your checkout sends notifications here; customers do not open it. Keep test URLs in the approved test setup and leave live checkout settings unchanged.
- Private activation link
- A private link for one customer to claim access. Never put it in shared checkout settings, on a website or in a general support reply.
If setup stops
- The option is not available
- Keep the saved product and existing checkout as they are. Use only actions your workspace currently offers; a planned provider or hidden option cannot be enabled from this guide.
- You don’t know whether a save worked
- Use the screen’s refresh action and review what is saved before trying another change. Don’t repeatedly submit, replace secrets or create duplicate connections to find out.
- The product, connection or sign-in changed
- Follow the prompt to refresh or reload, then check the account, product and saved connection. If a connection belongs to another product, choose the correct saved connection instead.
- A test URL expired or a limit was reached
- Stop sending test notifications and follow the status shown in the workspace. Prepare another URL only when the screen allows it and you deliberately start a new test. Refreshing does not extend an expiry.
- You need help
- Share the screen’s status, the action you tried and when it happened with your workspace administrator or support contact. Do not include passwords, Secret words, private activation links or test URLs. Remove these from screenshots too.
A saved setup, a test message, a real purchase, delivered email and successful login on your product’s website are separate checks. Don’t open live traffic based on one of them alone.
Review checkout availability · Return to the publisher guide