[Priyanshubhartistm]

Description

Adds unit specs for the four payment processors that had none, next to the existing lnbits and nwc ones (test/unit/payments-processors/). No production code changes.

For each processor:

• createInvoice: the request sent to the provider (url, body, amount unit, callback url / metadata, ttl) and the mapping of the response to an Invoice; msats are converted to whole sats where the provider takes sats; provider outages and responses without data are not swallowed.
• getInvoice: the request, every provider status mapped to InvoiceStatus (a status the provider adds later is never read as paid), confirmation dates, and error propagation.
• processor specifics: OpenNode's lightning_invoice / lightning fallback and amount / price fallback; Nodeless's 15 minute fallback expiry; LNURL's generated invoice id and verify-url polling.

Related Issue

Closes #903

Motivation and Context

These are the money-moving code paths for four providers. A misread status or a wrong amount unit is a funds bug, and nothing covered them.

How Has This Been Tested?

• The new specs pass (58 tests). Reverting a status mapping in transform.ts or changing OpenNode's ttl makes the matching spec fail.
• pnpm lint, pnpm check:deps, pnpm run build:check, pnpm run test:unit.

Screenshots (if appropriate):

Types of changes

• Non-functional change (docs, style, minor refactor)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my code changes.
• I added a changeset, or this is docs-only and I added an empty changeset.
• All new and existing tests passed.

[changeset-bot]

🦋 Changeset detected

Latest commit: e361ae7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge; the previous finding is fixed and no new actionable issues remain.

Summary

Adds unit tests for four payment processors without changing production code.

• Four payment providers now have unit specs for their invoice flows.

_{Reviews (2) · Last reviewed commit: "test(payments): use literal zebedee stat..." · Reviewed by Greptile}

[coveralls]

Coverage Report for CI Build 39466675129

Coverage increased (+0.5%) to 74.327%

Details

• Coverage increased (+0.5%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	11072
Covered Lines:	8652
Line Coverage:	78.14%
Relevant Branches:	5786
Covered Branches:	3878
Branch Coverage:	67.02%
Branches in Coverage %:	Yes
Coverage Strength:	812.57 hits per line

---

💛 - Coveralls