MantisBT - Issues

0011458: it should handle currency spec is misconfigured

Sun, 31 May 2026 22:31:04 +0200

consider this scenario:
* add a new currency in the spec (server config)
* add a product or order
* remove the currency from the spec
* restart server

now the SPA will be dead with no helpful info until config is fixed

0011457: need API spec for data export/import [2d]

Sun, 31 May 2026 22:25:25 +0200

With the current plan, this will mostly be the SQL dump of the schema.
Care will need to be taken with respect to the instance meta-data itself:
- migration of the private key should be optional
- instance meta-data is NOT in the per-instance SCHEMA but in the global table
- might want to introduce some kind of 'lock' state to prevent the instance
from being used (except for data-export) after the DB export was started

0009453: enable data export [14d]

Sun, 31 May 2026 22:24:59 +0200

Given that it is clear that there will be merchants that host their business data at some operator, we need to implement some data export functionality that enables a merchant to export all business data from one instance and to re-import that business data at another instance.

0011456: DB reconnect logic needs rework

Sun, 31 May 2026 22:20:44 +0200

When the database is restarted (or we otherwise loose the connection), our current
reconnect handling logic is not adequate. This needs a fix all the way down in libgnunetpq
and then all the way up in all components, as we clearly should have some notification logic.
We might also want to consider moving the general PREPARE macro helpers into libgnunetpq
to de-duplicate the code.
merchant may need some additional special handling to recover the now dynamic search_path.

0011183: swap ToS and KYC Auth steps in UX

Sun, 31 May 2026 14:35:45 +0200

The more common UX is that the ToS acceptance comes first, and the KYC AUTH step also takes too long to be a first step.
It would be better if KYC AUTH came last in the UX.
But we cannot change this in the protocol, so the idea is to allow the merchant to *ask* for the ToS acceptance first, and then to have the merchant backend 'fake' the ToS acceptance submission after it learns KYC AUTH is done.

This will be a MAJOR hack and requires both API changes, specification changes, and work in exchange and merchant.

0009424: taler-auditor-httpd incorrectly returns 404 when HTTP method does not match

Sun, 31 May 2026 14:29:48 +0200

We should instead return the HTTP status with the applicable HTTP methods.

0011446: Test KYC Auth reset via SQL

Sat, 30 May 2026 07:55:18 +0200

Directly related to 0011428, trying on TOPS/Stage if this works, i.e., doesn't create additional issues or even ends up w/ dysfunctional instances.

Three types of merchants shall be considered:

* kycauth_1_pending: merchant which entered an IBAN, but did not yet pay
* kycauth_2_kyc_ok: as above, but transfer fulfilled; exchange acceptance gotten
* kycauth_3_kyc_ok_and_withdraw: dito as w/ kycauth_2*, but additionally the merchant also acts as wallet user and withdrew money from the exchange he verified against as merchant, and doing so to the *very same IBAN* which was used as merchant (for IBAN settlements from paid orders)

0011454: eddsa helper process shuts down unexpectedly

Sat, 30 May 2026 00:14:28 +0200

In one particular harness test, the eddsa helper process shuts down unsolicitedly while the test is still running and uses the exchange.

0011231: wallet claims "fee" was being paid when wire transfer was simply less than amount specified in withdraw dialog

Fri, 29 May 2026 21:37:24 +0200

A beta tester could replay (after some successful transfers) the following unsuccessful transactions:
1. Bank transfer with minimal amounts for verification of the bank account before a deposit could be effectuated (Taler Wallet -> bank account). The transfer of CHF 0.01 from the bank account takes the same amount of time as a transfer bank account -> Taler Wallet (which is to be expected). But the CHF 0.01 from the bank account did not arrive anywhere, neither in the Taler Wallet nor back in the user's bank account. This was tested with Alpian Bank and PostFinance.

2. The KYC process needed to be performed over and over again for every deposit Taler Wallet -> bank
"I would expect to have to make exactly one transfer from a bank account to a wallet and then always be able to send money back. However, depending on the bank, it seems that KYC is required again when sending money back. It also seems that KYC expires after a few days and has to be done again."

3. Bank -> Taler Wallet with transfer amount too small, money arrives but flagged as "fee"
"If you create a transfer in the Taler Wallet for, say, CHF 10.00, but the transfer from the bank is only for CHF 5.00, CHF 5.00 will arrive in the wallet and CHF 5.00 will be listed as a “fee.” Basically, this works OK, but the naming is a bit strange."

4. Bank -> Taler Wallet with transfer amount too high --> money gets lost??
"If you create a transfer in the Taler Wallet for CHF 10.00, for example, but the bank transfers CHF 15.00, CHF 10.00 will arrive in the wallet. The extra CHF 5.00 will remain missing and will not be transferred back."

0010963: incoming wire transfer with truncated subject did not get bounced

Fri, 29 May 2026 21:29:48 +0200

(psql) select * from libeufin_nexus.incoming_transactions where incoming_transaction_id=156;

on *spec* (production!) shows an incoming wire transaction with a truncated wire transfer subject. However, there is no matching entry in the 'bounced_transactions' table, and (predictably) also none in the talerable_incoming_transactions table.

I don't think that should be possible. Didn't check Postfinance activities yet, but would like an explanation/investigation.
The logs are also not nice, the truncated wire transfer subject does not seem to have been logged at all. This should at least be a WARNING IMO.

0011277: Paying to a template not possible

Fri, 29 May 2026 21:29:29 +0200

The user "boipisiore" generates a QR code for a template. It makes an error : "Cette transaction a été annulée" (the transaction has been canceled) on his phone.
For this error, I do not see the problem.
On my phone it makes "solde insuffisant" (not enough money) whereas I have 50CHF.
For this error, there seams to be a confusion between the two currencies (BFH Fr and CHF) .

0011428: user stuck on KYC requirement, but merchant does not show it

Fri, 29 May 2026 21:28:47 +0200

We have a merchant-user who never did their KYC for their bank account (but the wallet used the bank account!), and now the merchant backend doesn't show 'kyc required', thus they cannot process orders/deposits. Very bad.

0011400: WebExtension "abort" without reaction

Fri, 29 May 2026 21:26:50 +0200

Seen while trying to receive a p2p payment from an iOS device, which was shown in the browser's Talet wallet as "pending to complete".

0011450: wallet-core handles expiration of proposed v1 contracts with choices badly

Fri, 29 May 2026 21:26:22 +0200

Steps:
* Scan payment QR code on https://shop.test.taler.net/
* Wait until payment deadline expires
* Scan again
* => wallet throws exception about choiceIndex instead of reporting expired transaction

The problem seems to be that we treat expired payments as already confirmed and try to repurchase.

```
case PurchaseStatus.Expired:
return handleConfirmed();
```

0009057: support subscription and discount tokens [meta]

Fri, 29 May 2026 21:26:22 +0200

This is a meta-bug, it includes support in wallet-core and the GUIs and the required changes to the database and the wallet-core API.

0010017: enable automatic monthly transfer to wallet via periodic transfer

Fri, 29 May 2026 21:25:32 +0200

We've had this request now from a customer in CH as well as from BEKI: They are used to doing automated periodic monthly wire transfers and would like them to automatically withdraw money into a Taler wallet. We should support this.

Note: requires also some exchange changes, as right now reserve public keys come with a UNIQUE constraint...

0010510: need support for v1 contracts incl. subscription and discounts in UI

Fri, 29 May 2026 21:25:14 +0200

Same as in the other wallets.

0011335: Review of strings on the settings page in the Merchant Backoffice UI

Fri, 29 May 2026 21:24:29 +0200

On the settings page in the Merchant Backoffice UI, a request for change makes sense: "Zahlungsdetails" --> "Zahlungsfrist" (in English: "Payment delay"). This is easy to do. Tested was v1.5.3 with instance talerstickers together with HM.

Moreover, the whole page needs a new feature in relation to the addition of time delays (under the scroll-down menu "Default cut-off times"): I suggest to insert plus symbols between the specific time delays (t.i. payment delay, refund delay, wire transfer delay) to clarify that these times are added to a period of time between payments and wire transfers that end up on the bank account (which is what merchants want to know in the first place).

After having reviewed the German strings in question this ticket will be then forwarded to the person in charge of the UI designs (t.i. contemporarily Vlada).

0011138: Implement empty wallet screen

Fri, 29 May 2026 21:23:50 +0200

Implement empty wallet screen for webex according to https://docs.taler.net/design-documents/086-wallet-design.html#empty-wallet

0011135: Implement empty wallet screen [meta]

Fri, 29 May 2026 21:23:45 +0200

Implement Empty Wallet screen according to https://docs.taler.net/design-documents/086-wallet-design.html#empty-wallet

0011245: CHF filter broken

Fri, 29 May 2026 21:23:09 +0200

Given cases where the same currency is used, but for different scopes, like in my case (seen in Android)

- BFH/CHF, restricted to snack machines at BFH, and
- TOPS/CHF (stage), used for testing purposes (cf. https://docs.taler.net/deployments/tops-stage-devtesting.html), not backed by real CHF money,
- TOPS/CHF (production), used for real CHF transfers under the Swiss sandbox license, backed by real money,

it happens that the sums displayed at various areas in the app (most visibly when paying something) are just wrong, because the various CHF currencies are mixed (as in: somehow summed) together, but sometimes also with sums which are not simply the sum of all individual CHF sums.

0010307: Wallet shows confusing error message when withdrawal KYC limit is reached

Fri, 29 May 2026 21:22:38 +0200

happens with version 1.0.8

0010415: 502 returned on order with unknown token family (input/output)

Fri, 29 May 2026 21:22:24 +0200

Happened in Ivan's demo on shop.test.taler.net, unclear why the TF is not gone, but if the TF is not there we would expect a 409 or 400, not a 502. But maybe the backend gave a 409/400 and the *Python* code just didn't handle that nicely?

0010369: WebExtension needs proper balances screen

Fri, 29 May 2026 21:21:45 +0200

We need to add a proper balances screen where we show currency balances and then also discount tokens, subscriptions and (in the future) other assets of the user in several tables/lists. The current approach of only showing one currency and selecting them with a drop-down will not work reasonably well if we add additional asset types.

0011172: send notification to merchant when KYC status changes [meta]

Fri, 29 May 2026 21:21:16 +0200

Right now, the merchant has to go to the backend to see the change. We should trigger an automatic notification.