KDPika Licensing Sign inStart free
API v1
Show all languages
Browse documentation

Choose a page in the navigation drawer.

KDPika Licensing · API v1 Beginner

Deliver licenses to customers

Stage 12: deliver licenses to customers with a clear outcome, verification steps and one next action.

On this page
Updated 2026-10-20 UTCDownload Markdown
Complete Integration Guide

Before you start: Protect tokens and identity, or bring the same completed Sandbox setup.

Stage 12 of 14 · 15 min
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14

Already completed this? Skip to the next stage →

What you will do

Choose one delivery route. Sending a key and protecting the software are separate tasks.

No-code manual route

  1. Open Sandbox [Licenses](/docs/v1/start/glossary#license) → New license.
  2. Choose the customer's product and plan, enter their email and create the key.
  3. Deliver it through your private customer channel. The full key is shown once.
  4. Inspect Devices and the license status for support, never request a password.

WooCommerce

  1. Install the official connector and connect your workspace.
  2. Use Import store products → Complete setup & enable sync to prepare App IDs, plans and mappings together. Existing IDs are reused.
  3. Review the shared device/access defaults once. Official subscription metadata comes from WooCommerce; inferred name-based periods need review.
  4. Test a confirmed store order and verify the key in the order and My Account.
  5. Keep Test/Live payment evidence, quotas and product permissions enforced.

The native connector is different from the advanced standalone store-service reference.

Another store or backend

Choose the matching sales-platform guide. A webhook is a server notification, not payment proof by itself.

  1. Verify the provider notification's signature using original raw bytes.
  2. Retrieve/confirm the current purchase with the provider and match product/customer/amount/state.
  3. Issue or update through a scoped management API key on your trusted backend.
  4. Save a durable purchase-to-license mapping and deduplicate retries.
  5. Handle cancellations, paid-through access, refunds and disputes without blind reissuance.

No-code automation still needs a trusted verification/fulfillment step; do not paste a developer key into public browser code.

Expected result

One eligible purchase produces the intended license, and repeated notifications do not duplicate it.

If it does not work

Customer software license sales are separate from Stripe/Mollie billing for your KDPika platform subscription. Delayed notifications and an unconfirmed payment must not unlock customer access.

Stage checklist

  • I chose one delivery route.
  • Confirmed purchase and license ownership match.
  • I tested duplicate delivery, cancellation and refund handling.

Next steps

Continue to Stage 13: Test the complete lifecycle

You are here: Stage 12 of 14.

Was this page helpful?

Choose an answer

Do not include personal data, license keys or credentials. Retained for up to 30 days. This is not a support inbox.

Edit this pageReport an issue

Search documentation

Arrow keys to move, Enter to open, Escape to close. Search stays in your browser.
Cookie settings