# Norelio Developers

> Norelio sells digital products and subscriptions on behalf of its partners: a buy button or product card on the partner's site or a payment created from the partner's server, Norelio's own payment pages (card or PayPal), delivery of codes, files, texts, links or a webhook to the partner's server, subscriptions with renewals, top-ups (credits bought by package or by amount and reported in the webhook), an access check for subscription access, a customer state endpoint, a return URL and a client reference. Norelio is the merchant of record and pays the partner out.

Start with [Quickstart](https://docs.norelio.eu/quickstart): the first payment from your server, with code for Next.js, Node.js and Python. To let a coding agent do the integration, give it the prompt from [Build with an AI agent](https://docs.norelio.eu/ai-agent).

The API answers at https://app.norelio.eu: the server API under /api/v1/, the access check and the machine-readable schema under /api/public/; payment pages open at https://pay.lis-system.eu/pay/{productId}. Webhooks are POSTed to the endpoint the partner saved in the Norelio cabinet and are signed with HMAC-SHA256. Everything a developer needs is in the sections below; keys, widget ids and webhook settings are issued by the partner in the cabinet, not by the API.

## Documentation

- [Quickstart](https://docs.norelio.eu/quickstart): The first payment from your server in about fifteen minutes: API key, product, create the payment, send the user to pay, verify the webhook signature, read the customer state and credit a top-up exactly once, with code for Next.js, Node.js and Python.
- [Build with an AI agent](https://docs.norelio.eu/ai-agent): A ready prompt for Cursor, Claude Code or any coding agent: it reads llms.txt and the OpenAPI document and integrates Norelio by the rules that matter — the key on the server, payments created server-side, verified webhook signatures, every event processed once.
- [Overview](https://docs.norelio.eu): What Norelio does for a developer and what you can build today: payment button and checkout panel, subscriptions, webhooks, access check, return URL and client reference.
- [Webhooks](https://docs.norelio.eu/webhooks): Events, the notification payload, delivery rules, payload versioning and signature verification with Node.js and Python examples.
- [Access check](https://docs.norelio.eu/access-check): Ask from your server whether a buyer's subscription access is paid and until when: request, response, grace period and error codes.
- [Create a payment from your server](https://docs.norelio.eu/checkouts): POST a product id and your account reference from your server and get a payment address to send the user to: request, response, warnings, error codes and the full flow with the webhook.
- [Customer state](https://docs.norelio.eu/customer-state): Read one buyer's subscriptions and purchases by your account reference or by email: fields, statuses and limits.
- [Top-ups](https://docs.norelio.eu/top-ups): Sell credits: a product with packages and a free amount, three ways to start the payment (widget attributes, direct checkout, server API), the credits in the webhook, a handler in Node.js and Python, refunds.
- [Client reference](https://docs.norelio.eu/client-reference): Pass your own account reference at checkout and get it back in every webhook for that order.
- [Return URL](https://docs.norelio.eu/return-url): Bring the buyer back to your site after payment, like success_url at payment providers: allowed sites, the attribute, the parameter and what the result page does.
- [Payment widget and checkout panel](https://docs.norelio.eu/widget): Embed a buy button or a product card on your site: the snippet, the attributes it reads, direct checkout and what your terms must contain, and the direct payment link.
- [Taxes and payouts](https://docs.norelio.eu/taxes-and-payouts): Who the merchant of record is, how VAT is handled for buyers inside and outside the EU, and how partners are paid.
- [Changelog](https://docs.norelio.eu/changelog): The notification payload version and the compatibility commitment.

## Machine-readable

- [OpenAPI 3.1](https://docs.norelio.eu/openapi.json): the access check, the machine-readable schema endpoint and every webhook event with its payload, as an OpenAPI document.
- [Full documentation](https://docs.norelio.eu/llms-full.txt): every section above in one Markdown file.