View Issue Details

IDProjectCategoryView StatusLast Update
0011107Talermerchant backendpublic2026-02-19 18:43
Reportervecirex Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status confirmedResolutionopen 
Target Version1.8 
Summary0011107: Backend for sms auth needs fixing for cases where number wrong (e.g., too short, too long, or invalid (like flipped digit))
DescriptionUnfortunately, from our current helper scripts we get status codes like 400 or 404 for the two gateway providers we have, when we do like

+41 79 NNN NN NN K, while K is too much
+41 79 NNN NN N, with a missing digit somewhere (e.g., at the end)
+41 79 NNN NN WN, with a W turning the number invalid (e.g., at the end)

or just any other number which clearly is wrong,
Steps To ReproduceDoing it wrong with a pattern above, the following happens (for both SMS auth providers, telesign and clicksend):

curl: (22) The requested URL returned error: 400
telesign failed.
Polling message status (message_id: 1F10D12F-2AFA-6988-9122-3549D9A5CD0D)...
curl: (22) The requested URL returned error: 404
clicksend failed.
All SMS providers failed.
taler-merchant-httpd@1b0bd36dc346:/usr/local/bin$
Additional InformationOf course this will also happen if it's utterly wrong, like just "+41", which currently even the backoffice SPA lets through.
TagsNo tags attached.

Relationships

related to 0011106 confirmedvecirex Phone numbers need proper checking 
child of 0011108 confirmed Error message when an SMS cannot be delivered (bc of invalid number) should be subtle 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-02-18 22:45 vecirex New Issue
2026-02-18 22:47 vecirex Relationship added related to 0011106
2026-02-19 02:30 vecirex Description Updated
2026-02-19 02:50 vecirex Relationship added related to 0011108
2026-02-19 18:42 Christian Grothoff Relationship deleted related to 0011108
2026-02-19 18:42 Christian Grothoff Relationship added child of 0011108
2026-02-19 18:43 Christian Grothoff Priority high => normal
2026-02-19 18:43 Christian Grothoff Status new => confirmed
2026-02-19 18:43 Christian Grothoff Target Version => 1.8