View Issue Details

IDProjectCategoryView StatusLast Update
0010194Talermerchant backendpublic2025-08-25 02:01
ReporterFlorian Dold Assigned ToChristian Grothoff  
PriorityurgentSeverityfeatureReproducibilityhave not tried
Status assignedResolutionopen 
Product Version1.0 
Target Version1.1 
Summary0010194: merchant backend should improve bank account selection when creating orders
DescriptionIn particular, the merchant should prefer accounts that are supported by the exchanges relevant for the order.

Right now, the merchant can select bank accounts where payment of the order would be impossible, since the supported exchanges do not support the wire method of the bank account.
TagsNo tags attached.

Activities

Christian Grothoff

2025-07-20 16:46

manager   ~0025540

e4f7102c..12951e28 contains a possible fix, should be checked.

Christian Grothoff

2025-07-20 16:48

manager   ~0025541

Note that the wallet test
    {
      "name": "kyc-fail-recover-double",
      "timeSec": 2.997,
      "status": "fail"
    },
fails, and we should double-check if the merchant is too permissive or if the test needs to be updated.

Florian Dold

2025-08-20 19:22

manager   ~0025669

The test now pass, it it was an unrelated issues (wrong assumptions in the test).

@Christian: Can we resolve this? Or do we want/need a test in taler-harness for the new behavior of the merchant? Is it tested at all so far?

Christian Grothoff

2025-08-20 19:52

manager   ~0025671

I thought there was one test in the taler-harness now already. I'm OK with this being resolved for now, but also OK with more tests ;-).

Florian Dold

2025-08-25 02:00

manager   ~0025687

I've implemented a proper test, and the merchant *almost* does the right thing, but it returns the same exchange twice!

You can reproduce it with:
$ taler-harness run-integrationtests merchant-acctsel

You'll get something like this:

[...]
    "exchanges": [
      {
        "master_pub": "317HC716S2M9QSMEYX21SFV3VEKCS327GXBRHZKT83Q1SSM6NNSG",
        "priority": 1024,
        "url": "http://localhost:8181/",
        "max_contribution": "TESTKUDOS:5"
      },
      {
        "master_pub": "317HC716S2M9QSMEYX21SFV3VEKCS327GXBRHZKT83Q1SSM6NNSG",
        "priority": 1024,
        "url": "http://localhost:8181/",
        "max_contribution": "TESTKUDOS:5"
      }
    ],
[...]

FATAL: test failed with exception AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:

2 !== 1

Issue History

Date Modified Username Field Change
2025-07-16 15:46 Florian Dold New Issue
2025-07-16 17:11 Florian Dold Severity minor => feature
2025-07-16 20:24 Christian Grothoff Assigned To => Christian Grothoff
2025-07-16 20:24 Christian Grothoff Status new => assigned
2025-07-16 20:24 Christian Grothoff Product Version => 1.0
2025-07-17 14:32 Christian Grothoff Priority normal => urgent
2025-07-20 16:46 Christian Grothoff Note Added: 0025540
2025-07-20 16:48 Christian Grothoff Note Added: 0025541
2025-07-30 11:19 Christian Grothoff Assigned To Christian Grothoff => Florian Dold
2025-08-20 19:22 Florian Dold Assigned To Florian Dold => Christian Grothoff
2025-08-20 19:22 Florian Dold Status assigned => feedback
2025-08-20 19:22 Florian Dold Note Added: 0025669
2025-08-20 19:52 Christian Grothoff Note Added: 0025671
2025-08-20 19:52 Christian Grothoff Assigned To Christian Grothoff => Florian Dold
2025-08-25 02:00 Florian Dold Note Added: 0025687
2025-08-25 02:01 Florian Dold Assigned To Florian Dold => Christian Grothoff
2025-08-25 02:01 Florian Dold Status feedback => assigned