Status and limits
What has been verified against the Nuvion sandbox, what has not, and what the plugin does not do yet.
Pre-release (0.x)
Published on npm as @umohpyro/better-auth-nuvion (unofficial, under the author's scope). Expect changes to the API before 1.0. What changed in each version is in the changelog.
Verified
On the Nuvion sandbox, with real requests:
- Creating a hosted-checkout funding session and paying it with the sandbox bank.
- Real signed
inflows.completedwebhooks: the header names, the ISO 8601 timestamp, and the HMAC over{timestamp}.{raw body}all verify. The inflow carries the funding session'sunique_referenceandnarration, and ameta.funding_session_id, so matching by reference works. - Creating the counterparty and
book-transferpayment detail the plugin needs, between two accounts of one entity. - Confirm before acting: a real settled funding session is confirmed, and a wrong amount, reference, currency or an unknown session is refused; a real finished transfer is found by its reference. A real
outflows.completeddelivered to a webhook inbox, with a valid signature, settled the payment through the confirm path. - Real book transfers split a paid checkout, with the signed
outflows.completedandinflows.completedwebhooks settling the payment. - Refunds as reversal legs, settled by real webhooks.
- Real failed transfers: an
outflows.failedevent marks the leg failed with Nuvion's reason, the payment becomespartial, and a retry completes it. A failed transfer burns itsunique_reference, which is why legs use a new reference per attempt. - Reconciliation against Nuvion's transfer status.
- Webhook delivery: a failed delivery is retried about a minute later with the same event id and a new signature, and events can arrive out of order. The plugin handles both.
On Nuvion production (20 November 2026, NGN, between two accounts of one entity, real signed webhooks to a webhook inbox):
- A split leg of ₦1.00 sent as a book transfer through the plugin's own code, with the counterparty and payment detail created on first use. The signed
outflows.completedverified, was confirmed against Nuvion's own record of the transfer, and the payment settled. - A refund of that payment: the reversal leg moved the ₦1.00 back, its
outflows.completedverified and settled, and the payment becamerefunded. - Balances matched exactly what the transfers should have done, with no fee on a book transfer.
- The pay-in was simulated, because NGN has no hosted checkout. The confirm-before-acting check on a funding session has been run on the sandbox only.
On real databases: SQLite, Postgres (PGlite and a server over TCP), MariaDB 10.4 configured like MySQL 8, and the Drizzle and Prisma 7 adapters on Postgres, including 8 simultaneous deliveries of the same event producing exactly one split.
Against a simulated Nuvion API: the whole flow, including retries, refunds, de-duplication, fee math (property-tested to sum exactly) and migrations.
Not verified yet
- A real hosted-checkout payment on Nuvion production. Open Banking takes a GBP or EUR payer, so it needs a UK or EU bank account.
- MySQL 8 on Linux, and Drizzle or Prisma on MySQL or SQLite.
outflows.cancelledandoutflows.refundedfor book transfers. The sandbox has no way to cancel a transfer, andoutflows.refundedis a card-network event, so only Nuvion's sample payloads cover them.
Not built yet
| Gap | Today |
|---|---|
outflows.refunded mapped back to a payment | Acknowledged only. It is a card-network event, and book transfers never produce it |
| Paying the customer back on refund | Not possible from Nuvion's data: its refund API is for card payments, and an open-banking inflow carries no payer bank details. Paying to bank details your app collects is a fraud risk. Use the onRefunded hook to pay back through your own process |
| Multi-currency splits | One currency per payment, one Nuvion account per organization. Splitting across currencies needs FX conversion, which the plugin does not do |
| Subscriptions | Nuvion's API documents no mandate or recurring collection for open banking, so every payment needs the customer to approve it at their bank |
Amounts use JavaScript numbers (safe for fiat).