Skip to content
productpay

THE FREE PRODUCTPAY WORKSHOP

Turn a purchase into
a better relationship.

A practical walkthrough with Sam Bakker: help customers find their products, get personal support, and feel looked after.

Sam BakkerYour host · ProductPayNo email signup needed
RECORDING IN PREPARATION

A good experience
starts after checkout.

The video is not available yet. You can read the written workshop and first-product checklist now.

Read the workshop

THE WRITTEN WORKSHOP

Read along.
Take your next step.

This is the written version prepared for the upcoming recording. Examples are illustrative, not live customer data.

CHAPTER 01

Start with the customer

Hi, I’m Sam Bakker. This workshop is about a part of selling digital products that is easy to overlook: what happens after somebody buys. They have made a decision to trust you. The next thing they need is usually quite simple. Where do I go? How do I get started? And who can help if I get stuck?

That is the problem we are building ProductPay to address. Not another checkout to replace the one you already use. A clearer place for your customers to find their connected products, and a more personal way to get support from the people behind them.

You might recognize the familiar support conversation: somebody cannot find their access instructions, you ask which product they mean, and then you try to match the email address to a purchase. Each individual step sounds small. Together, they put the work on both you and your customer.

Our aim is to bring those pieces closer together. I want to show you a simple customer journey, how support fits into it, and the first product setup. As you watch, think of one product you already sell. You do not need to move your whole business at once.

The examples in this workshop use fictional customers and a demonstration product. They show how the experience works, not a claim about measured revenue, reduced refunds, or a guaranteed amount of time saved.

CHAPTER 02

Give every buyer a way back

Let’s start on the customer side. Imagine Alex has bought a digital product from you. Alex is not thinking about integrations, transaction systems or the different tools you use to run your business. Alex wants to get to the product.

The first part of that journey is the thank-you and access page. Its job is to make the next action understandable. Not to present a wall of administration, but to help a buyer move from purchase to access.

Later, Alex can come back to My products to find connected purchases. That last word matters: connected. ProductPay does not scan somebody’s inbox or automatically find every digital product they have ever bought. It works with the products and purchase records connected to it.

Look at this example. The product has a recognizable name, a clear action to open it, and a way to get help. For someone who is less comfortable with technology, those familiar choices matter more than adding another menu full of options.

This does not replace the product itself. If your course or software lives in another system, its access destination still needs to work. We are making the route to it clearer, and giving the customer somewhere familiar to return.

Here is the useful question to ask about your own setup: if a buyer comes back in three months, will they know where to begin? The goal is a repeatable answer, not just a one-time email that they have to find again.

CHAPTER 03

Make support a conversation

Now let’s say Alex has a question. This is where access and support should feel like parts of the same experience. The customer should not have to work out which of your tools to use or repeat the product name at every step.

In ProductPay, a product has a support page. Your team can see the request with its product context, and use the customer record to review the purchase information that is available. A connected purchase can give you useful facts when you need to understand what the customer bought.

There is an important boundary here. A question submitted before purchase verification is not the same as a verified purchase. We should not treat an email address or a message saying “I bought this” as proof of entitlement. ProductPay keeps that distinction visible rather than pretending every ticket has an authenticated receipt.

But a security boundary does not have to make the interaction impersonal. Your support profile can tell the customer who is replying. A customer can share their name and profile details. Where a name is known and appropriate to use, a friendly greeting is better than treating somebody as a string of characters.

On the publisher side, private notes can help you retain useful context. That is different from a public reply. A note for your team should not be sent to the customer by accident, and it should not become a reason to collect unnecessary personal information.

For a refund question, the available purchase details can help you find the relevant transaction. The actual refund still belongs in the original payment provider’s workflow. ProductPay is not promising that every payment can be identified from any email address, or that it refunds purchases on your behalf.

The principle is straightforward: keep the useful context close, keep private information within the right boundaries, and make it clear that there is a person helping. That is the relationship we want the software to support.

CHAPTER 04

Connect your first product

So how do you start? Choose one product. Give it a name customers will recognize, add the appropriate product details, and set the destination they should reach when they open it.

Next, review where customers pay. JVZoo: Limited pilot. 7 checkout connections planned. The checkout catalogue shows each provider’s current scope. A planned connection cannot be connected yet; you can save the product and connect later. Subscription access, renewals and cancellations are not supported by these checkout connections yet. Your ProductPay publisher subscription is separate.

For an eligible connection, follow the instructions supplied by your publisher workspace. Your checkout and affiliate arrangements stay with the checkout provider. The product destination and your ProductPay workspace subscription are separate. Do not assume that pasting one page URL completes the purchase connection.

Then, when the workspace confirms publication, there are two customer links to keep together. The first is the thank-you or access page. The second is the support page, where customers can ask for help with that product. Follow the current provider guide for how these links fit its checkout.

These are reusable product links. They are not a particular customer’s private activation link. That distinction is worth remembering: a private link should never be copied into a public checkout setting or reused for another customer.

Before real customers use it, test the journey with the approved test process. Does the purchase connection produce the expected record? Does the access page lead to the correct place? Can the customer get back to their product? Does the support page clearly identify the product and your team?

Pages ready, connection tested, purchase verified, email delivered and successful login on another website are different facts. A nice-looking thank-you page is not proof that a purchase has been verified. This is why I would begin with one product you can check carefully, then expand once you understand the process.

For your own checklist, keep that order: product and access, checkout, then customer links. Confirm the provider’s availability, keep private activation links separate, and test the customer journey. That gives you a practical starting point without turning your first setup into a project to reorganize everything you sell.

CHAPTER 05

Choose your next step

If you sell digital products and want a clearer experience after checkout, ProductPay is being built for that job. You have seen the core idea: a place for the buyer to return, product-specific help, and useful context for the people providing support.

The publisher plan is USD $49 per month, or $490 for a year. The annual option is one annual payment, not a monthly charge. It is $98 less than paying the monthly price twelve times. Both options have the same core features.

This is a subscription for your publisher workspace. It is not a fee for your buyers to use ProductPay to access their connected purchases or ask you for help. Your own products and their prices remain separate.

We are preparing paid signups. Before they open, we will publish the final plan limits and commercial terms, and finish testing billing, account activation, renewals and cancellation. There is no payment to make on this preview website today.

Your next step is to review the plan page and the setup checklist. Pick the product you would start with, and ask whether this would make the experience simpler for the people who buy from you. If you are here as a customer looking for something you already purchased, use My products—you do not need a publisher plan.

Thank you for spending this time with me. A good sale starts a relationship. Let’s make what happens next feel just as considered.