View Issue Details

IDProjectCategoryView StatusLast Update
0005409Talerobsolete componentpublic2023-12-03 01:25
Reportershivamkohli Assigned ToChristian Grothoff  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionnot fixable 
Product Versiongit (master) 
Target Version0.8Fixed in Version0.8 
Summary0005409: Payto URI
DescriptionAdd paytoURI in the order.
Ask for payto URI while a new merchant is registering on codeless payment platform.
TagsNo tags attached.

Relationships

related to 0005433 closedChristian Grothoff design and implement KYC APIs 

Activities

Christian Grothoff

2018-07-28 11:46

manager   ~0013153

We'll need more than a payto://-URI from merchants, as per recent discussions with Marcello. Marcello has been working on a merchant registration page in the Taler backend. So please either coordinate with him, or just leave this one to Marcello entirely.

Marcello Stanisci

2018-07-28 11:53

reporter   ~0013155

Would also be great to know something more about 'codeless' payments; does a description exist somewhere?

Christian Grothoff

2018-07-28 11:55

manager   ~0013156

I don't know if more documentation was written yet, but from GSoC we have this description: "To accept payments with GNU Taler currently some custom (though simple!) code must be written to integrate with an existing web shop or frontend. The goal of this project (codeless payments) is to create a component that sits between the seller's frontend and the GNU Taler merchant backend. This component should have a web interface, where payment buttons or payment forms can be configured that can by copy-pasted into the seller's frontend as static HTML/JS. Bonus goals are inventory management, where the seller can configure the available stock for an item, and will get notified when their stock runs low."

Christian Grothoff

2018-07-28 11:56

manager   ~0013157

Anyway, Marcello, did you do any documentation / API specs on the 'merchant registration' logic that you proposed to add to the back office yet? Because I think this is precisely what this bug is about and how it should be addressed ;-)

Marcello Stanisci

2018-07-28 13:34

reporter   ~0013160

Last edited: 2018-07-28 13:35

I did not spec anything for now; as per recent discussion with you, it seems that this data should be collected at _installation_ time, that makes me wonder again if you intend to get the sysadmin enter this information. In this case, there is no need to spec anything for the back-office site.

Christian Grothoff

2018-07-28 15:34

manager   ~0013161

Not the sysadmin, but the last step of the backend install could be something like telling the admin that to create/fully configure (?) in instance, they should point the business people to a particular form that they should fill out (per instance).

shivamkohli

2018-07-28 16:25

reporter   ~0013162

Codeless payment is a platform for the merchant where they can manage their inventory and simultaneously create a 'Buy Now' button for the specific product. This code can be directly copy pasted on the seller's frontend and can be used for 'Pay with Taler'. The documentation for 'codeless' payment is under progress and with be available soon.
For the payto://-URI, I will contact Marcello.

Christian Grothoff

2019-09-09 15:56

manager   ~0014878

shivam: do you still plan to work on this?

shivamkohli

2019-09-11 15:16

reporter   ~0014885

Yes, I can work on this. Please, can you help me get started?

Christian Grothoff

2020-01-12 22:43

manager   ~0015262

Marcello writes (truncated): I *try* to recollect the pieces. At that time I was supposed to write some Web interface to let business people enter merchant's bank details into their configuration.

This appeared to match the 'codeless' job, since merchants should at some point give their bank details there as well. That was my
only "involvement".

But on my side, I have *no idea* why the issue suggests to add the merchant's payto-URL into the order.

Christian Grothoff

2020-09-05 00:00

manager   ~0016861

I think nobody quite understands at this point what the payto-change has to do with codeless, so let's just consider this bug "not fixable" as we don't understand it ourselves ;-).

Issue History

Date Modified Username Field Change
2018-07-21 00:11 shivamkohli New Issue
2018-07-21 00:11 shivamkohli Status new => assigned
2018-07-21 00:11 shivamkohli Assigned To => shivamkohli
2018-07-28 11:46 Christian Grothoff Note Added: 0013153
2018-07-28 11:47 Christian Grothoff Assigned To shivamkohli => Marcello Stanisci
2018-07-28 11:53 Marcello Stanisci Note Added: 0013155
2018-07-28 11:55 Christian Grothoff Note Added: 0013156
2018-07-28 11:56 Christian Grothoff Note Added: 0013157
2018-07-28 12:03 Marcello Stanisci Target Version => 0.6
2018-07-28 13:34 Marcello Stanisci Note Added: 0013160
2018-07-28 13:35 Marcello Stanisci Note Edited: 0013160
2018-07-28 15:34 Christian Grothoff Note Added: 0013161
2018-07-28 16:25 shivamkohli Note Added: 0013162
2018-09-15 11:02 Christian Grothoff Relationship added related to 0005433
2019-09-09 15:56 Christian Grothoff Note Added: 0014878
2019-09-11 15:16 shivamkohli Note Added: 0014885
2019-11-14 22:40 Christian Grothoff Target Version 0.6 => 0.7.1
2020-01-12 22:43 Christian Grothoff Note Added: 0015262
2020-03-29 22:08 Christian Grothoff Product Version => git (master)
2020-03-29 22:08 Christian Grothoff Target Version 0.7.1 => 0.8.1
2020-07-24 11:57 Christian Grothoff Target Version 0.8.1 => 0.8
2020-07-24 12:02 Christian Grothoff Target Version 0.8 => 0.9.1
2020-09-04 14:37 MS Assigned To Marcello Stanisci => MS
2020-09-05 00:00 Christian Grothoff Assigned To MS => Christian Grothoff
2020-09-05 00:00 Christian Grothoff Status assigned => resolved
2020-09-05 00:00 Christian Grothoff Resolution open => not fixable
2020-09-05 00:00 Christian Grothoff Fixed in Version => 0.8
2020-09-05 00:00 Christian Grothoff Note Added: 0016861
2020-09-05 00:01 Christian Grothoff Status resolved => closed
2020-09-05 00:01 Christian Grothoff Target Version 0.9.1 => 0.8
2023-12-03 01:25 Christian Grothoff Category codeless payments => obsolete componet
2023-12-11 20:08 Florian Dold Category obsolete componet => obsolete component