diff options
Diffstat (limited to 'template')
| -rw-r--r-- | template/gsoc-codeless.html.j2 | 206 | ||||
| -rw-r--r-- | template/investors.html.j2 | 141 | ||||
| -rw-r--r-- | template/merchants.html.j2 | 181 |
3 files changed, 0 insertions, 528 deletions
diff --git a/template/gsoc-codeless.html.j2 b/template/gsoc-codeless.html.j2 deleted file mode 100644 index c2c297a7..00000000 --- a/template/gsoc-codeless.html.j2 +++ /dev/null @@ -1,206 +0,0 @@ -{% extends "common/base.j2" %} -{% block body_content %} - <div class="jumbotron"> - <div class="container text-center"> - <h1>{{ _("GSoC 2018: Codeless Payment") }}</h1> - <h6>{{ _("Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and guidance of Florian Dold.") }}</h6> - </div> - </div> - - <div class="container"> - <div class="col-lg-12"> - <h2 id="overview">{{ _("Overview") }}</h2> - <p> - {% trans %} - Codeless payment is a component that sits between the seller's - frontend and the GNU Taler merchant backend. This component has a - web interface, where payment buttons are configured. Registered - merchants can manage their inventory and simultaneously create a - 'Buy Now' button for a specific product. This code can be directly - copy pasted on the seller's frontend and can be used for 'Pay with - Taler'. - {% endtrans %} - </p> - </div> - </div> - - <div class="container"> - <div class="col-lg-6"> - <h2 id="overview">{{ _("Use Cases") }}</h2> - <p> - {% trans %} - The various use cases and features of codeless payment are: - {% endtrans %} - </p> - <ul> - <li> - {% trans %} - The primary use case is the registration of the merchant. The - codeless payment backend provides a secure django authenticated - login to the merchant. The registered merchant can add inventory - (both digital as well as physical) in their stocks. They can - manage inventory and simultaneously create a 'Buy Now' button for - the product. The merchant also monitors the orders placed and - updates the status of the order which helps in shipment tracking. - {% endtrans %} - </li> - <li> - {% trans %} - A merchant has the flexibility to add two types of inventory as follows: - {% endtrans %} - <ul> - <li> - {% trans %} - The merchant can upload digital inventory (like a PDF or HTML - page) via the codeless payments frontend and the user can then - purchase it and view the version hosted by the codeless - payment frontend. - {% endtrans %} - </li> - <li> - {% trans %} - The merchant can add any physical inventory available in his - stocks. While adding these inventory, the seller is prompted - to add minimum quantity of product that is required to be - maintained in the stock. Whenever the stocks run below this - limit the seller would be notified (currently this feature has - not been added but soon email notification would be added). - {% endtrans %} - </li> - </ul> - </li> - <li> - {% trans %} - The buyers will access the seller's frontend where the code for - the 'Buy Now' button is present. When this button is triggered, - they are redirected to codeless payment backend and eventually - redirected to the payment page. After successful payment, the - buyer can also track their shipment for physical products or - view the digital version hosted by the codeless payment - frontend. - {% endtrans %} - </li> - <li> - {% trans %} - The other use case of the codeless payment backend is to handle - the event when the 'Buy Now' button is triggered on the seller's - frontend. To perform the payment the backend communicates with - merchant backend api. After successful payment, the users are - redirected to the fulfilment page. - {% endtrans %} - </li> - </ul> - <h2 id="overview">{{ _("Dynamic Merchant Instance") }}</h2> - <p> - {% trans %} - The documentation for the API to dynamically manage merchant - instance can be found - <a href="https://docs.taler.net/api/api-merchant.html#dynamic-merchant-instance">here</a>. - {% endtrans %} - </p> - </div> - <div class="col-lg-6"> - <img src="{{ url_static('images/UseCaseDiagram.png') }}" alt="{{ _("Use Case Diagram")}}" style="float: right; margin: 5px 5px 5px 5px;" width="100%"> - </div> - </div> <!-- /container --> - - <div class="container-fluid c_acronym"> - <div class="container"> - <h2 id="documentation">{{ _("Link to the contributions made") }}</h2> - <p> - </p> - <ul> - <li>{{ _("Codeless Payment Backend") }} - (<a href="https://git.taler.net/codeless.git/">{{ _("Link")}}</a>) - </li> - <li>{{ _("Documentation to dynamically manage Merchant Instances") }} - (<a href="https://git.taler.net/api.git/commit/?id=53b3fbc3a882975b4ca8ef70d7ae256c9c17a23e">{{ _("Link")}}</a>) - </li> - </ul> - <p> - </p> - </div> - </div> - - <div class="container"> - <div class="col-lg-12"> - <h2 id="overview">{{ _("Future Work") }}</h2> - - <p> - {% trans %} - The backend of codeless payment is very robust and can be easily - extended as per the requirements. It is adaptive to add new features - to this framework. But as per the discussion and the scope of this - project, there are various features that will be soon added in the - Codeless Merchant Backend. The list of future work is as follows: - {% endtrans %} - </p> - <ul> - <li> - {% trans %} - To send email notification to the merchant when the stocks run - below a certain limit. The minimum quantity required to be - maintained in the stocks is currently taken from the - merchant(specific to each product) but no such notification system - is designed. - {% endtrans %} - </li> - - <li> - {% trans %} - To add API access to the merchant backend via the codeless payment - service. Basically, it would be used as a hosting platform for - multiple merchants. There would be an additional user interface - part in the codeless payment service where a logged-in merchant - can generate an API key. This API key can be used to access the - functionality of the merchant backend in a controlled way. After - requesting an API key, the page would display the generated key - and a base URL for the API to use by the seller, which is handled - by the codeless payments service. - {% endtrans %} - </li> - - <li> - {% trans %} - Mapping every seller account to a separate merchant backend - instance. This is not required for a simple version of codeless - payments, but as soon as API access for sellers, this is a useful - feature. The codeless payment service then can also double as a - hosting service for merchants. - {% endtrans %} - </li> - - <li> - {% trans %} - To add various analytics for the merchant. Various analysis - could be performed on the orders placed for the respective - merchant. Some of the analysis that can be performed are - displaying the most frequently purchased product, some insights - about the shipment tracking, analysis of products based on - delivery location, etc. For this part, dicussions and some more - research have to be done before proceeding to the - implementation. - {% endtrans %} - </li> - </ul> - </div> - </div> <!-- /container --> - - <div class="container"> - <div class="row"> - <h2 id="documentation">{{ _("Screenshots") }}</h2> - <div class="col-lg-4"> - <h3>{{ _("Home page")}}</h3> - <img src="{{ url_static('images/home.png') }}" height="240" align="middle"> - </div> - <div class="col-lg-4"> - <h3>{{ _("Product page")}}</h3> - <img src="{{ url_static('images/product.png') }}" height="240" align="middle"> - </div> - <div class="col-lg-4"> - <h3>{{ _("Shipment Tracking")}}</h3> - <img src="{{ url_static('images/shipment.png') }}" height="240" align="middle"> - </div> - </div> - </div> -{% endblock body_content %} diff --git a/template/investors.html.j2 b/template/investors.html.j2 deleted file mode 100644 index 4fb50259..00000000 --- a/template/investors.html.j2 +++ /dev/null @@ -1,141 +0,0 @@ -{% extends "common/base.j2" %} -{% block body_content %} - - <div class="jumbotron"> - <div class="container text-center"> - <h1>{{ _("Invest in Taler!") }}</h1> - <div class="col-lg-12"> - <p> - {% trans %} - We have created a company, Taler Systems SA in - Luxembourg.<br> - Please contact <tt>invest@taler.net</tt> - if you want to invest in Taler. - {% endtrans %} - </p> - </div> - </div> - </div> - - - <div class="container adorn_h3_bracket"> - <div class="row"> - <div class="col-lg-4"> - <h3>{{ _("The Team") }}</h3> - - <p> - {% trans %} - Our team combines world-class business leaders, - cryptographers, software engineers, civil-rights - activists and academics. We are unified by a vision - of how payments should work and the goal of - imposing this vision upon the world. - {% endtrans %} - </p> - - <p> - {% trans %} - We are currently supported by - <a href="http://www.inria.fr/">Inria</a>, - the French national institute for research in informatics and - automation, and the - <a href="https://renewablefreedom.org/">Renewable Freedom Foundation</a>. - {% endtrans %} - </p> - </div> - <div class="col-lg-4"> - <h3>{{ _("The Technology") }}</h3> - - <p> - {% trans %} - All transactions in Taler are secured using - <a href="bibliography.html">modern cryptography</a> - and trust in all parties is minimized. Financial damage is bounded - (for customers, merchants and the exchange) even in the case that - systems are compromised and private keys are stolen. Databases - can be audited for consistency, resulting in either the detection - of compromised systems or the demonstration that participants were - honest. Actual transaction costs are fractions of a cent. - {% endtrans %} - </p> - </div> - <div class="col-lg-4"> - <h3>{{ _("The Business") }}</h3> - <p> - {% trans %} - The scalable business model for Taler is the operation - of the payment service provider, which converts money from - traditional payment systems (MasterCard, SEPA, UPI, - Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous - electronic coins in the same currency. The customer - can then redeem the electronic coins at a merchant, - who can exchange them for money represented using - traditional payment systems at the exchange. The - exchange charges fees to facilitate the transactions. - {% endtrans %} - </p> - </div> - </div> - </div> - - - <div class="container-fluid c_acronym"> - <div class="container"> - <h2>{{ _("The Business Case") }}</h2> - <div class="row"> - <div class="col-lg-4"> - <a href="{{ url('presentations/investors2018.pdf') }}"> - <img border=0 class="center-block" width=64 height=64 alt="PDF" src="{{ url_static('images/pdf.svg') }}"> - <br> - <p align="center">{{ _("Download") }}</p> - </a> - - <p> - {% trans %} - Our <a href="financial-news.html">financial news</a> page - explains in English how Taler can impact current developments in - the global payment market. - {% endtrans %} - </p> - </div> - <div class="col-lg-4" id="canvas-left" style="display:none"> - <canvas id="the-canvas-left"></canvas> - </div> - <div class="col-lg-4" id="canvas-right" style="display:none"> - <canvas id="the-canvas-right"></canvas> - </div> - <script type="text/javascript" src="{{ url_dist('js/pdf.min.js') }}"></script> - <script type="text/javascript" src="{{ url_dist('js/pdf-view.js') }}"></script> - </div> - </div> - </div> - - - <div class="container"> - <div class="row"> - <div class="col-lg-12"> - <h2 id="overview">{{ _("Running a Taler payment service operator") }}</h2> - - <p> - {% trans %} - The payment service operator runs the <em>Taler exchange</em>. - The exchange charges <b>transaction fees</b> to customers or merchants. - Its operational expenses are from wire transfers with the banking - system and the operation of the computing infrastructure. - {% endtrans %} - </p> - - <p> - <ul> - <li>{{ _("Cryptographic operations, bandwidth and storage costs are less than 0.01 cent per transaction.") }}</li> - <li>{{ _("Multiple Taler transactions can be aggregated into larger wire transfers to merchants to minimize wire transfer costs.") }}</li> - <li>{{ _("Protocol allows the exchange to charge fees for any expensive operation (withdraw, deposit, refresh, refund or aggregated wire transfers).") }}</li> - <li>{{ _("Partnership with banks establishes consumer trust.") }}</li> - <li>{{ _("Partnership with free software community enables rapid deployment.") }}</li> - </ul> - </div> - </div> - </div> - - -{% endblock body_content %} diff --git a/template/merchants.html.j2 b/template/merchants.html.j2 deleted file mode 100644 index 95836059..00000000 --- a/template/merchants.html.j2 +++ /dev/null @@ -1,181 +0,0 @@ -{% extends "common/base.j2" %} -{% block body_content %} - <div class="jumbotron"> - <div class="container text-center"> - <h1>{{ _("Advantages for Merchants") }}</h1> - - <p> - {% trans %} - Taler is a cost-effective electronic payment system - which provides you with cryptographic proof that - the payment worked correctly within milliseconds. - Your Web customers pay with previously unknown - levels of convenience without risk of fraud. - {% endtrans %} - </p> - </div> - </div> - - <div class="container adorn_h3_bracket"> - <div class="row"> - <div class="col-lg-4"> - <h3>{{ _("Fast") }}</h3> - - <p> - {% trans %} - Processing transactions with Taler is fast, - allowing you to confirm the transaction with your - customer virtually immediately. Your customers - will appreciate that they do not have to type in - credit card information and play the "verified - by" game. By making payments significantly - more convenient for your customers, you may be able - to use Taler for small transactions that would not - work with credit card payments due to the mental - overhead for customers. - {% endtrans %} - </p> - - </div> - <div class="col-lg-4"> - <h3>{{ _("Secure") }}</h3> - - <p> - {% trans %} - You will have cryptographic proof of payment from the - Taler payment service provider. With Taler you never - handle sensitive customer account information and thus - do not have to undergo any particular security audits - (such as PCI DSS). Your systems will have customer - contracts with qualified signatures for all - transactions which you can use in court in case of - disputes. - {% endtrans %} - </p> - - </div> - <div class="col-lg-4"> - <h3>{{ _("Free") }}</h3> - - <p> - {% trans %} - Taler is free software, and you can use the - liberally-licensed reference code as a starting - point to integrate Taler into your services. To use - Taler, you do not need to pay license fees, and the - free software development model will ensure that - you can select from many competing integrators for - support. - {% endtrans %} - </p> - - </div> - </div> - <div class="row"> - <div class="col-lg-4"> - <h3>{{ _("Cheap") }}</h3> - <p> - {% trans %} - Taler is uses efficient cryptographic constructions with low - bandwidth and storage requirements. Combined with Taler's strong - security which makes fraud impossible, Taler payment service - providers can operate with very low overhead and - thus offer low transaction fees. - {% endtrans %} - </p> - </div> - <div class="col-lg-4"> - <h3>{{ _("Flexible") }}</h3> - <p> - {% trans %} - Taler can be used for different currencies (such as - Euros, US Dollars or Bitcoins) and any amount, limited - only by applicable regulation and what denominations - the payment service provider supports. - {% endtrans %} - </p> - </div> - <div class="col-lg-4"> - <h3>{{ _("Ethical") }}</h3> - <p> - {% trans %} - Taler prevents tax evasion and money laundering. - Taler's protocols are efficient and do not use wasteful - proof-of-work calculations. Taler encourages - transparency by providing an open standard and free - software reference implementations. - {% endtrans %} - </p> - </div> - </div> - </div> - - <div class="container-fluid c_acronym"> - <div class="container"> - <h2 id="documentation">{{ _("Manuals for merchants") }}</h2> - <ul> - <li>{{ _("The GNU Taler merchant backend operator manual") }} - (<a href="https://docs.taler.net/merchant/backend/html/manual.html">html</a>, - <a href="https://docs.taler.net/merchant/backend/pdf/manual.pdf">pdf</a>) - </li> - <li>{{ _("The GNU Taler Web shop integration tutorial (PHP)") }} - (<a href="https://docs.taler.net/merchant/frontend/php/html/tutorial.html">html</a>, - <a href="https://docs.taler.net/merchant/frontend/php/pdf/tutorial.pdf">pdf</a>) - </li> - <li>{{ _("The GNU Taler Web shop integration tutorial (Python)") }} - (<a href="https://docs.taler.net/merchant/frontend/python/html/tutorial.html">html</a>, - <a href="https://docs.taler.net/merchant/frontend/python/pdf/tutorial.pdf">pdf</a>) - </li> - </ul> - </div> - </div> - - - <div class="container"> - <div class="col-lg-6"> - <h2 id="overview">{{ _("The GNU Taler Merchant Backend") }}</h2> - <p> - {% trans %} - Merchants process payments using the Taler backend: - {% endtrans %} - </p> - <ul> - <li> - {% trans %} - The backend <b>signs</b> and <b>stores</b> the - complete terms of offers made by the merchant to customers. - For this, the merchant's frontend needs to give the - customer's order in a JSON format to the backend. - {% endtrans %} - </li> - - <li> - {% trans %} - The backend <b>validates</b> payments received from - the wallet and <b>executes</b> them with the Taler - payment service provider (the exchange). For this, - the merchant's frontend must pass the payment - request through to the Taler backend and check the - HTTP status code that is returned. - {% endtrans %} - </li> - - <li> - {% trans %} - The backend can <b>list</b> completed transactions - and <b>map</b> wire transfers to sets of business - transactions, including the exact terms of each - contract. - {% endtrans %} - </li> - </ul> - </div> - <!-- - FIXME: When we wrap this img in a div of class col, - FIXME: the image ends up overlaping the footer. - --> - <img src="{{ svg_localized('images/backend') }}" - alt="{{ _("customer perspective")}}" - class="img-fluid"> - </div> <!-- /container --> -{% endblock body_content %} |