View Issue Details

IDProjectCategoryView StatusLast Update
0011625Talermerchant backoffice SPApublic2026-07-30 19:18
ReporterFlorian Dold Assigned Tosebasjm  
PriorityhighSeverityblockReproducibilityhave not tried
Status assignedResolutionopen 
Target Version1.6 
Summary0011625: KYC auth QR code and payto URI does not include amount and reference/subject
DescriptionThe SPA just shows the exchange's plain payto without the additional information.
TagsNo tags attached.

Relationships

related to 0011624 resolvedvecirex deploy merchant (1.6.9) on lifeline 

Activities

sebasjm

2026-07-11 01:00

developer   ~0029140

previous code was taken the payto from here

https://docs.taler.net/core/api-merchant.html#get--management-instances-$INSTANCE-kyc

  // Array of full payto://-URIs with
  // wire transfer instructions (including
  // optional amount and subject) for a KYC auth wire
  // transfer. Set only if this is (still) required
  // to get the given exchange working.

now the new endpoint

https://docs.taler.net/core/api-merchant.html#post-[-instances-$INSTANCE]-private-accounts-$H_WIRE-kycauth

  // Full payto:// URL of the (exchange) bank account to which the
  // money should be sent, excludes the wire subject and the amount.
  target_payto: string;


... what stop us for being consistent, here the whole WireTransferInstructionDetail could be just and payto:// with params. now some params are in the payto (receiver name, postal) and some are not and the client software needs to add it. (!!)

sebasjm

2026-07-11 01:15

developer   ~0029141

1c7b743ab..20c181844

adds
 * the credit_amount to the payto
 * subject when type is simple to the payto as message param
 * qr_reference_number when the type is CH_QR_BILL as message param

completely brittle

sebasjm

2026-07-11 01:15

developer   ~0029142

i think this should come from the merchant backend in the payto instead of relying on the client

Christian Grothoff

2026-07-30 18:42

manager   ~0029314

Florian and I agree that this should NOT be changed in the REST API and be solved 100% client-side.

Florian Dold

2026-07-30 19:18

manager   ~0029315

I don't really understand what's brittle about it, it's trivial to write a helper function to transform the subject into a full payto. I've added on here:

commit b4d1c980d688c68628b0293b2f313c28990cf17f (HEAD -> master, origin/master, origin/HEAD)
Author: Florian Dold <florian@dold.me>
Date: Thu Jul 30 19:17:04 2026 +0200

    util: add paytoFromTransferSubject helper

Issue History

Date Modified Username Field Change
2026-07-09 16:50 Florian Dold New Issue
2026-07-09 16:50 Florian Dold Status new => assigned
2026-07-09 16:50 Florian Dold Assigned To => sebasjm
2026-07-09 16:50 Florian Dold Relationship added related to 0011624
2026-07-11 01:00 sebasjm Note Added: 0029140
2026-07-11 01:15 sebasjm Note Added: 0029141
2026-07-11 01:15 sebasjm Assigned To sebasjm => Christian Grothoff
2026-07-11 01:15 sebasjm Status assigned => feedback
2026-07-11 01:15 sebasjm Note Added: 0029142
2026-07-11 20:03 Christian Grothoff Status feedback => assigned
2026-07-30 18:42 Christian Grothoff Note Added: 0029314
2026-07-30 18:42 Christian Grothoff Assigned To Christian Grothoff => sebasjm
2026-07-30 18:43 Christian Grothoff Assigned To sebasjm => Florian Dold
2026-07-30 19:18 Florian Dold Note Added: 0029315
2026-07-30 19:18 Florian Dold Assigned To Florian Dold => sebasjm