Skip to content

Add Allowance v1.2.1 - #858

Open
BenGWeeks wants to merge 1 commit into
lnbits:mainfrom
BenGWeeks:add-allowance-v1.2.1
Open

BenGWeeks wants to merge 1 commit into
lnbits:mainfrom
BenGWeeks:add-allowance-v1.2.1

Conversation

@BenGWeeks

Copy link
Copy Markdown

Add Allowance v1.2.1 for vetting. Allowance schedules individual recurring payments from an LNbits wallet to a Lightning address or LNURL-pay endpoint, in sats or fiat. Its focus is wallet-based allowance management, anchored schedules and clear per-payment history.

The extension uses LNbits payment services, wallet authorization and existing dependencies. Automatic retries are bounded; pending or uncertain payments retain their identity. Eligible failed or skipped occurrences can be paid explicitly after confirmation, preserving the regular schedule. Recipient requests enforce public HTTPS, with exact operator-owned exceptions for split DNS. This is a native Python extension, not a WASM component.

Validation:

  • python3 check.py allowance passes, including archive hash, required files, config compatibility and icon.
  • The submitted tagged source archive contains exactly the same file bytes as the published installation ZIP; native fresh installation and reinstallation passed on LNbits 1.6.1 with FakeWallet and no external network.
  • Release CI passed SQLite regressions, PostgreSQL and native installation/upgrade checks on LNbits 1.6.0, 1.6.1 and 1.6.2. Testing scope and operator guidance are documented in the repository.
  • Browser checks cover inactive allowance creation/edit/delete, payment-history actions and mobile FAQ layout. Payment fixtures use synthetic data and intercepted APIs; settlement tests use FakeWallet.

Screenshots show the released UI with synthetic allowance data, not live recipients or funds.

Allowance management

Payment history

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant