{% if not ajax %} {% extends "base.html" %} {% endif %} {% from "macros.jinja" import window_vars with context %} {% block scripts %} {{ window_vars(user) }}{% endblock %} {% block page %}
Tell us something about your extension:
  • This is the first step, you can return and change it.
  • The `name` and `sort description` fields are what the users will see when browsing the list of extensions.
  • The `id` field is used internally and in the URL of your extension.

  • Define what settings your extension will have.
  • You can choose if each user has its own settings or if the settings are global (set by the admin).
Each user can set its own settings for this extension. Settings are set by the admin and apply to all users of the extension
  • The owner of the extension manages this data. It can add, remove and update instances of it.
  • Some fileds are present by default, like created_at, updated_at and extra.
  • This data is created by users of the extension. Usually when they submit a form or make a payment.
  • The owner of the extension can view this data, but should not modify it.

  • Most extensions have a public page that can be shared (this page will still be accessible even if you have restricted access to your LNbits install).
Public page title Select the field from the   (Owner Data) that will be used as a title for the public page.
Public page description Select the field from the   (Owner Data) that will be used as a description for the public page.
Public page inputs
  • Select the fields from the   (Client Data) that will be shown as inputs in the public page form.
  • You can select multiple fields.
  • A corresponding input field will be created for each selected field.
Generate Action Button
  • If enabled, the public page will have a button to perform an action (e.g. generate a payment request).
  • The action will use the selected input fields from   (Client Data) as parameters.
  • A corresponding REST API endpoint will be created.
Generate Payment Logic
  • If enabled, the endpoint will create an invoice from the submitted data and the UI will show the QR code with the invoice.
  • A listener will be created to check for the pay event.
  • You must map the fieds.
Wallet
  • Select the field from the   (Owner Data) that represents the wallet which will generate the invoice and receive the payments.
  • Only fields with the type Wallet will be shown.
Currency
  • Select the field from the   (Owner Data) that represents the currency which will be used to for the amount.
  • Only fields with the type Currency will be shown.
  • Empty if you want to use sats.
Amount
  • Select the field from the   (Owner Data) or   (Client Data) that represents the amount (in the selected currency).
  • Only fields with the type Integer and Float will be shown.
Paid Flag
  • Select the field from the   (Client Data) that will be set to true when the invoice is paid.
  • Only fields with the type Boolean will be shown.
  • The extension builder uses caching to speed up the build process.
  • This action clears old data and redownloads the Extension Builder Stub release.
  • Installs the extension directly to this LNbits instance.
  • The extension will be enabled by default, and available to all users.
Builds the extension and downloads a zip file with the code. You can then install it manually in your LNbits instance.
{% endblock %}