path: root/docs/project.bib

@misc{taler-user-guide,
    author       = {GNU Taler},
    title        = {GNU Taler User Guide},
    url          = {https://docs.taler.net/taler-user-guide.html},
    howpublished = {\url{https://docs.taler.net/taler-user-guide.html}}
}

@misc{panetta-speech-march-30,
    author              = {Fabio Panetta},
    role                = {Member of the Executive Board of the ECB},
    year                = {2022},
    month               = {March},
    day                 = {30},
    speech-location     = {Brussel, Committee on Economic and Monetary Affairs of the European Parliament},
    title               = {A digital euro that serves the needs of the public: striking the right balance},
    url                 = {https://www.ecb.europa.eu/press/key/date/2022/html/ecb.sp220330_1~f9fa9a6137.en.html},
    howpublished        = {\url{https://www.ecb.europa.eu/press/key/date/2022/html/ecb.sp220330_1~f9fa9a6137.en.html}}
}

@misc{study-new-digital-payment-methods,
    author       = {Kantar Public (Verian since November 2023), on behalf of ECB},
    title        = {Study on New Digital Payment Methods},
    year         = {2022},
    month        = {March},
    url          = {https://www.ecb.europa.eu/euro/digital_euro/investigation/profuse/shared/files/dedocs/ecb.dedocs220330_report.en.pdf},
    howpublished = {\url{https://www.ecb.europa.eu/euro/digital_euro/investigation/profuse/shared/files/dedocs/ecb.dedocs220330_report.en.pdf}},
}

@misc{srf-espresso-cc-fraud,
    author       = {Peter Fritsche},
    year         = {2022},
    month        = {April},
    title        = {Keine Rückerstattung bei «verifizierten» Geldbezügen},
    url          = {https://www.srf.ch/news/panorama/kreditkarten-betrug-keine-rueckerstattung-bei-verifizierten-geldbezuegen},
    howpublished = {\url{https://www.srf.ch/news/panorama/kreditkarten-betrug-keine-rueckerstattung-bei-verifizierten-geldbezuegen}}
}

@misc{cc-fraud-types,
    author       = {Stadtpolizei Zürich, Kommissariat Prävention},
    title        = {Betrugsarten},
    url          = {https://www.card-security.ch/betrugsarten/},
    howpublished = {\url{https://www.card-security.ch/betrugsarten/}}

}

@misc{pci-dss,
    author       = {PCI Security Standards Council},
    title        = {PCI Data Security Standard},
    url          = {https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf},
    howpublished = {\url{https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf}}
}

@misc{wallee-till-sdk,
    author       = {Wallee},
    title        = {Wallee Android Till SDK},
    url          = {https://github.com/wallee-payment/android-till-sdk},
    howpublished = {\url{https://github.com/wallee-payment/android-till-sdk}}
}

@misc{wallee-transaction-process,
    author       = {Wallee},
    title        = {Transaction States},
    url          = {https://app-wallee.com/de-de/doc/payment/transaction-process},
    howpublished = {\url{https://app-wallee.com/de-de/doc/payment/transaction-process}}
}

@misc{wallee-pcidss-compliance,
    author       = {Wallee},
    title        = {Transaction States},
    url          = {https://app-wallee.com/de-de/doc/payment},
    howpublished = {\url{https://app-wallee.com/de-de/doc/payment}}
}

@misc{wallee-transaction-service-docs,
    author       = {Wallee},
    title        = {Transaction Service},
    url          = {https://app-wallee.com/de-de/doc/api/web-service#transaction-service},
    howpublished = {\url{https://app-wallee.com/de-de/doc/api/web-service#transaction-service}}
}

@misc{wallee-refund-service-docs,
    author       = {Wallee},
    title        = {Refund Service},
    url          = {https://app-wallee.com/de-de/doc/api/web-service#refund-service},
    howpublished = {\url{https://app-wallee.com/de-de/doc/api/web-service#refund-service}}
}

@misc{wallee-available-connectors,
    author       = {Wallee},
    title        = {Payment Connectors},
    url          = {https://app-wallee.com/connectors},
    howpublished = {\url{https://app-wallee.com/connectors}}
}

@misc{wallee-api-authentication,
    author = {Wallee},
    title  = {Authentication},
    url    = {https://app-wallee.com/en-us/doc/api/web-service#_authentication},
    howpublished = {\url{https://app-wallee.com/en-us/doc/api/web-service#_authentication}}
}

@misc{rfc8959,
    series =    {Request for Comments},
    number =    8959,
    howpublished =  {RFC 8959},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8959},
    url =       {https://www.rfc-editor.org/info/rfc8959},
    author =    {Mark Nottingham},
    title =     {{The "secret-token" URI Scheme}},
    pagetotal = 5,
    year =      2021,
    month =     jan,
    abstract =  {This document registers the "secret-token" URI scheme to aid in the identification of authentication tokens.},
}

@misc{rfc8905,
    series =    {Request for Comments},
    number =    8905,
    howpublished =  {RFC 8905},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8905},
    url =       {https://www.rfc-editor.org/info/rfc8905},
    author =    {Florian Dold and Christian Grothoff},
    title =     {{The 'payto' URI Scheme for Payments}},
    pagetotal = 12,
    year =      2020,
    month =     oct,
    abstract =  {This document defines the 'payto' Uniform Resource Identifier (URI) scheme for designating targets for payments. A unified URI scheme for all payment target types allows applications to offer user interactions with URIs that represent payment targets, simplifying the introduction of new payment systems and applications.},
}

@misc{rfc3986,
    series =    {Request for Comments},
    number =    3986,
    howpublished =  {RFC 3986},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC3986},
    url =       {https://www.rfc-editor.org/info/rfc3986},
    author =    {Tim Berners-Lee and Roy T. Fielding and Larry M Masinter},
    title =     {{Uniform Resource Identifier (URI): Generic Syntax}},
    pagetotal = 61,
    year =      2005,
    month =     jan,
    abstract =  {A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. {[}STANDARDS-TRACK{]}},
}

@misc{rfc3629,
    series =    {Request for Comments},
    number =    3629,
    howpublished =  {RFC 3629},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC3629},
    url =       {https://www.rfc-editor.org/info/rfc3629},
    author =    {François Yergeau},
    title =     {{UTF-8, a transformation format of ISO 10646}},
    pagetotal = 14,
    year =      2003,
    month =     nov,
    abstract =  {ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.},
}

@misc{rfc7617,
    series =    {Request for Comments},
    number =    7617,
    howpublished =  {RFC 7617},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC7617},
    url =       {https://www.rfc-editor.org/info/rfc7617},
    author =    {Julian Reschke},
    title =     {{The 'Basic' HTTP Authentication Scheme}},
    pagetotal = 15,
    year =      2015,
    month =     sep,
    abstract =  {This document defines the "Basic" Hypertext Transfer Protocol (HTTP) authentication scheme, which transmits credentials as user-id/ password pairs, encoded using Base64.},
}

@misc{fips-180-4,
  author = {Quynh Dang},
  title = {Secure Hash Standard},
  year = {2015},
  month = {2015-08-04},
  publisher = {Federal Inf. Process. Stds. (NIST FIPS), National Institute of Standards and Technology, Gaithersburg, MD},
  doi = {https://doi.org/10.6028/NIST.FIPS.180-4},
  language = {en},
}

@misc{fips-202,
    author = { National Institute of Standards and Technology },
    title = {SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions},
    url = {https://doi.org/10.6028/NIST.FIPS.202},
    howpublished = {\url{https://doi.org/10.6028/NIST.FIPS.202}},    
}

@misc{gnunet-gana,
    author = {GNUnet Project},
    title = {The GNUnet Assigned Numbers Authority (GANA)},
    url = {https://gana.gnunet.org/},
    howpublished = {\url{https://gana.gnunet.org/}}
}

@misc{taler-bank-integration-api,
    author = {Taler},
    title = {Taler Bank Integration API},
    url = {https://docs.taler.net/core/api-bank-integration.html},
    howpublished = {\url{https://docs.taler.net/core/api-bank-integration.html}}
}

@misc{taler-wire-gateway-api,
    author = {Taler},
    title = {Taler Wire Gateway HTTP API},
    url = {https://docs.taler.net/core/api-bank-wire.html},
    howpublished = {\url{https://docs.taler.net/core/api-bank-wire.html}}
}

@misc{taler-wire-gateway-api-authentication,
    author = {Taler},
    title = {Taler Wire Gateway HTTP API},
    url = {https://docs.taler.net/core/api-bank-wire.html#authentication},
    howpublished = {\url{https://docs.taler.net/core/api-bank-wire.html#authentication}}
}

@misc{taler-bank-core-authentication,
    author = {Taler},
    title = {Authentication},
    url = {https://docs.taler.net/core/api-corebank.html#authentication},
    howpublished = {\url{https://docs.taler.net/core/api-corebank.html#authentication}}
}

@misc{taler-design-document-49,
    author = {Taler},
    title = {Authentication},
    url = {https://docs.taler.net/design-documents/049-auth.html},
    howpublished = {\url{https://docs.taler.net/design-documents/049-auth.html}}

}

@misc{wallet-withdrawal,
    author       = {Taler},
    title        = {Withdrawal},
    url          = {https://docs.taler.net/taler-wallet.html#withdrawal},
    howpublished = {\url{https://docs.taler.net/taler-wallet.html#withdrawal}}
}

@misc{postgres-notify,
    author = {PostgreSQL},
    title = {NOTIFY},
    url = {https://www.postgresql.org/docs/current/sql-notify.html},
    howpublished = {\url{https://www.postgresql.org/docs/current/sql-notify.html}}
}

@misc{postgres-listen,
    author = {PostgreSQL},
    title = {LISTEN},
    url = {https://www.postgresql.org/docs/current/sql-listen.html},
    howpublished = {\url{https://www.postgresql.org/docs/current/sql-listen.html}}
}

@misc{golang-contexts-and-structs,
    author       = {Jean de Klerk, Matt T. Proud},
    title        = {Contexts and structs},
    year         = {2021},
    month        = {February},
    day          = {24},
    url          = {https://go.dev/blog/context-and-structs},
    howpublished = {\url{https://go.dev/blog/context-and-structs}}
}

@misc{golang-share-by-communicating,
    author = {Go},
    title  = {Share by communicating},
    url    = {https://go.dev/doc/effective_go#sharing},
    howpublished = {\url{https://go.dev/doc/effective_go#sharing}},
}

@misc{golang-goroutines,
    author = {Go},
    title  = {Goroutines},
    url    = {https://go.dev/doc/effective_go#goroutines},
    howpublished = {\url{https://go.dev/doc/effective_go#goroutines}},
}

@book{loosley-coupled,
    author = {Kaye, Doug},
    title = {Loosely Coupled: The Missing Pieces of Web Services},
    year = {2003},
    isbn = {1881378241},
    publisher = {RDS Press},
    doi = {10.5555/996526}
}

@article{ieee-soa-architecture-patterns,
    author = {Stal, Michael},
    title = {Using Architectural Patterns and Blueprints for Service-Oriented Architecture},
    year = {2006},
    issue_date = {March 2006},
    publisher = {IEEE Computer Society Press},
    address = {Washington, DC, USA},
    volume = {23},
    number = {2},
    issn = {0740-7459},
    abstract = {Some experts view service-oriented architecture simply as a stack of XML Web services protocols. From a more conceptual point of view, however, SOA represents a paradigm consisting of a set of architectural principles for building loosely coupled software systems. Actually, the SOA paradigm applies not only to XML Web services but also to other technologies such as email clients and servers and message-oriented middleware. Software patterns can express almost all architecture principles that span SOA technologies. This architecture-centric approach offers the means to understand service-oriented infrastructures and to build SOA applications that meet operational and developmental properties. Additionally, best practice pattern systems and catalogs can be derived from these architectural principles to illustrate how to implement SOA applications effectively and efficiently. Last but not least, an architectural description of SOA helps to change or extend the paradigm when necessary--for example, to address additional problems such as the support of integrative and adaptive SOA approaches.This article is part of a special issue on software architecture.},
    journal = {IEEE Softw.},
    month = {mar},
    pages = {54–61},
    numpages = {8},
    keywords = {Distributed Applications, Distributed Objects, Middleware/Business Logic, Patterns, Software Architecture},
    doi = {10.5555/1128592.1128710}
}

@book{event-driven-architecture,
    author = {Rocha, Hugo},
    year = {2022},
    month = {01},
    title = {Practical Event-Driven Microservices Architecture: Building Sustainable and Highly Scalable Event-Driven Microservices},
    isbn = {978-1-4842-7467-5},
    doi = {10.1007/978-1-4842-7468-2}
}