Deliver to your customers

This page describes what happens between a customer paying and that customer being able to use your product, and how little of it you have to do yourself.

The short answer is that delivery is automatic. Monaiq issues the license, mints the credentials inside the buyer’s own account and emails them a link to it. You do not send keys, and you should not.

At checkout

A buyer can reach checkout from the marketplace, from your storefront page or from inside your own product if you have built the purchase in.

They verify their email address with a one-time code entered inline, then pay. There is no separate signup step to complete first, which means a buyer who has never heard of Monaiq before does not have to make an account before they can buy from you.

The license

Payment produces a license. The license records the product it unlocks, the features that come with the offering they bought, and how it is billed. It appears in the buyer’s account at monaiq.com/manage/licenses.

Paid provisioning is asynchronous, so this is not instantaneous. The license appears in Licenses within a minute or two of the payment going through.

Note

Tell customers what to expect if your own onboarding depends on the license existing. A minute or two of nothing is normal, not a failure.

Credentials

If your product checks licenses in code, the buyer needs a credential. A one-seat purchase hands one back, and the buyer can issue more from that seat’s detail page inside their signed-in account. The code is also how what they bought reaches your application, wherever they bought it: accept a pasted one.

A license code belongs to that one seat: it authorizes and meters that seat and reaches nothing else in the buyer’s account. The buyer can issue one per machine, label each, and revoke any of them on their own. That is what makes it safe for your application to store one.

Credentials are shown once, at issue, and only ever inside the signed-in account. Nothing sends them by email, and neither should you. If a customer says they have lost theirs, point them at that seat’s detail page to issue another and revoke the old one — there is nothing for you to re-send.

The emails Monaiq sends

The buyer gets a welcome and license delivery email that links their Licenses page, and a receipt for each payment that links their billing page. A buyer offered a free license against an address they have not yet proved gets a claim email instead, described below. Later mail covers the exceptions: a failed payment, an expiring card, a pending cancellation. All of it points back into their account rather than carrying anything sensitive itself.

Selling inside your own product

Not every sale should start on a marketplace page. Monaiq supports an embedded purchase flow, so a customer can buy an offering without leaving your application. The license, the credentials and the emails work exactly as they do above.

That path needs code, so it lives in Integrate rather than here. If your development is AI-assisted, the Monaiq tools include guidance for building the purchase flow, covered in AI-assisted setup.

Starting a checkout from an email address

Your own backend can start a checkout for an address your buyer typed, rather than for a buyer who is already signed in to Monaiq. Nothing is provisioned for that address until the person behind it is proved, and how they prove it depends on the price.

A paid offering proves it with the payment. The address goes to Stripe as the prefilled email, the buyer pays, and only then is the account resolved or created and the license issued. The delivery email links their license page, and their first sign-in links the account to it.

A free or trial offering proves it with a claim. Monaiq records the intent and hands your backend a claim link: send the buyer there at once, in the same browser. The page names you and the product, they confirm, prove the address with a one-time code, and are returned to your ReturnUrl. The license is created on that confirmation, and your result read flips from pending to completed with the credential. The same link is emailed to the address only as a fallback, some minutes later, for a buyer who closed the tab. The link is good for seven days; after that the result reads failed.

An address that already has a Monaiq account gets no shortcut on the free path: the claim is required either way. That is deliberate — it is what stops one seller attaching a license to somebody else’s account without their knowledge, and it means an address that is simply mistyped costs nothing but an unread email.

Two limits keep that honest and neither needs anything from you: one open offer is kept per offering and address, so a repeat submit re-sends nothing, and an address receives at most five claim emails an hour across all sellers.

What you do afterwards

Nothing, for a working sale. We bill the customer every period, raise the invoices and pay you out. Get paid covers the money, including refunds and what happens when a customer’s payment fails.