Skip to content
Kiragu MainaSystems workspace
Systems onlineSend a brief
All tools

Paystack Digital Product Shop

Keep the purchase record, verify the payment, and make the right file available even when an email needs another delivery attempt.

Creators selling templates, guides, or other downloadable files through Paystack.

Visual examples. Plain language. Go at your own pace.

Paystack Digital Product Shop

Package preview. Illustrations use sample data.

Payment to downloadExample
Order for your template
Payment awaiting confirmation Download locked

No real payment is made.

The challengePayment sent. Where is my file?
Illustration only. These are sample screens and values.

Slide 1 / 6

“I paid. Where is my template?”

Imagine your first buyer pays, closes the checkout tab, and waits for an email that never arrives. You need a purchase record you can check when they ask for help.

  • A return to the shop alone is not proof of payment.
  • A missed email should not erase a confirmed order.
1 of 6

What this means for your project

Help customers pay for a digital product and get their download.

Your first sale should feel like a win.

You wake up to your first template sale, followed by “I paid. Where is my download?” The buyer closed a tab and the email arrived late. This skill helps you build the checks and recovery steps that connect a confirmed payment to the file, even when the journey is interrupted.

How would I use this with AI?

A skill is a set of instructions and examples for your AI coding assistant. You bring your idea and your project. The skill gives the assistant a process to follow.

  1. Tell your AI what you want to build and share the package instructions.
  2. Work through the setup together. You may need accounts or tools listed below.
  3. Review the changes and test them before putting them on your live site.

This is a package you use while building, not a finished website or a service that runs it for you.

Not sure where to start? Ask about a project like yours.

Explore the example

Made-up example
  1. Create order
  2. Confirm payment
  3. Allow download
  4. Send email

Starting point

Payment notice is late: order still waiting

What changes

Check payment again: download access granted once

Try delaying a payment notice, then checking the payment again. Repeat the notice to see that it does not create extra download access. All payments here are made up.

Rehearse an imagined template purchase. Payment updates and orders are invented; no real money moves.

See how it works

Step 1 of 6

“I paid. Where is my template?”

Imagine your first buyer pays, closes the checkout tab, and waits for an email that never arrives. You need a purchase record you can check when they ask for help.

Starting situationA buyer returns from a payment page run by the payment service
Where it breaksReturning to the shop does not prove the buyer paid
Made-up example. Try the interactive preview to see what changes.
  • A return to the shop alone is not proof of payment.
  • A missed email should not erase a confirmed order.
About this example: Inspect the sample

Step 2 of 6

Give the purchase a path back to the file

Keep the order and download access separate from email delivery. Once payment is verified, the buyer’s access can remain available while a failed email is retried.

BeforeOrder waiting: no download access
AfterPayment confirmed: download access granted once, with email delivery that can be retried
Made-up example. Try the interactive preview to see what changes.
  • Remember the exact file version and price they ordered.
  • Connect the receipt page so the buyer can reach their download.
About this example: Inspect the sample

Step 3 of 6

Confirm the money before unlocking the file

Save the order, check it with Paystack, then grant access when the reference, amount, and currency match. Keep unfinished steps available for checking or retrying.

  1. Create the order
  2. Open the payment page
  3. Check the payment result
  4. Grant download access once
Steps shown in the example.
  • Repeated payment updates must not create duplicate access or delivery jobs.
  • If the provider’s reply is lost, check what happened before trying again.
About this example: Inspect the sample

Step 4 of 6

Rehearse the awkward purchase

Step through a sample order with a delayed confirmation. Watch when the file becomes available and what still needs attention.

What to tryTry delaying the payment notice, checking payment again, then repeating the notice
Expected resultChecking confirms the example payment and grants access. The repeated notice adds no extra access
Made-up example. Try the interactive preview to see what changes.
  • The demonstration uses invented payment data.
  • A “paid” button label does not establish payment.
  • Use the package examples to rehearse delivery failures and removing future access too.
Try the example
About this example: Inspect the sample

Step 5 of 6

Start with the whole purchase in view

Give your coding AI the example payment connection, private download handling, and recovery tools. Rehearse the problems before a real buyer meets them.

SKILL.md
Instructions for connecting payment confirmation to download access
scripts/
Example payment connection and recovery tools
examples/
Invented orders and setup examples
tests/
Checks for payment matches, repeated updates, and removing access
What the package contains. Check the release details for the exact file list.
  • A saved order, payment checks, and a queue for delivery attempts
  • Setup guidance and checks before accepting real money
  • Tools to check downloads and remove future access when required
About this example: Inspect the sample

Step 6 of 6

For creators ready to connect their own services

This fits a creator selling downloadable files through Paystack. The package gives you building blocks; your live shop still needs an eligible account, storage, hosting, and email.

What you need
  • Node.js 20 or later to run the sample purchases locally; these examples need no Paystack account or real payment
  • For real sales, your own Paystack account that is approved for the payments and currencies you intend to accept
  • Private file storage and a durable database, meaning order records survive a server restart
  • A server, a background worker that retries unfinished jobs, and an email delivery service; production also needs secure sign-in, encrypted web connections (HTTPS), and monitoring
Limits to knowThis example makes no real payment and does not contact a payment service
Check what you need and what the product can do before choosing it.
  • Provider activation, fees, taxes, and sales policies are yours to arrange.
  • Email retries can produce duplicates unless your sender prevents them.
  • Removing access cannot recall files already downloaded.
About this example: Inspect the sample

What you receive

  • Checkout with a saved record of the price and file version ordered
  • Checks on payment notifications and protection against granting the same access twice
  • Private downloads, a queue for delivery attempts, and recovery examples
  • Sample purchases using test data and a checklist for going live
See the files in the package
SKILL.md
Instructions for connecting payment confirmation to download access
scripts/
Example payment connection and recovery tools
examples/
Invented orders and setup examples
tests/
Checks for payment matches, repeated updates, and removing access

What you need to get started

  • Node.js 20 or later to run the sample purchases locally; these examples need no Paystack account or real payment
  • For real sales, your own Paystack account that is approved for the payments and currencies you intend to accept
  • Private file storage and a durable database, meaning order records survive a server restart
  • A server, a background worker that retries unfinished jobs, and an email delivery service; production also needs secure sign-in, encrypted web connections (HTTPS), and monitoring

What you can check here

Package version 1.0.0 / page version 3

  • Inspect the sample

    The interactive preview uses invented data to explain the steps. It does not show customer results or evidence of increased sales.

Will it work with your tools?

Codex and Node.jsExample setup only
Paid package version 1.0.0. Check the package compatibility record for the exact setups tested. Other tools, hosting services, and live provider connections need validation in your own setup.

Before you choose

Read the paid skill terms for permitted use, what your purchase includes, help, and refunds.

  • One purchase licenses one individual or organisation to use and modify this version in unlimited own and client projects, including commercial work. Do not resell the standalone package, sublicense it as a competing package, redistribute it publicly, or share it with unrelated purchasers. Later releases may be sold separately; no lifetime updates are promised.
  • Real sales require your own eligible Paystack account, hosting, and file delivery setup.
  • Paystack activation, fees, taxes, and your sales policies are separate responsibilities.
Does returning from checkout unlock a download?

No. Your server must verify a matching payment with Paystack before granting download access. Returning to the shop alone is not proof.

What if email delivery fails?

Download access remains recorded and available through the receipt page while email delivery retries. Your site needs to connect that page for buyers.