Taler exchange

LASTNAME@taler.net
ceo AT taler.net."
msgstr ""

#: copyright.html.j2:6
msgid "Copyright Assignment"
msgstr ""

#: copyright.html.j2:8
msgid ""
"Contributors to GNU Taler with Git access must sign the copyright assignment to ensure that the GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
"development of the GNUnet and GNU Taler projects is satisfied."
msgstr ""

#: copyright.html.j2:17
msgid ""
"The agreements ensure that the code will continue to be made available "
"under free software licenses, but gives developers the freedom to move code "
"between GNUnet and GNU Taler without worrying about licenses and the company "
"the ability to dual-license (for example, so that we can distribute via App-"
"stores that are hostile to free software)."
msgstr ""

#: copyright.html.j2:25
msgid ""
"Minor contributions (basically, anyone without Git access) do not require "
"copyright assignment. Pseudonymous contributions are accepted, in this case "
"simply sign the agreement with your pseudonym. Scanned copies are "
"sufficient, but snail mail is preferred."
msgstr ""

#: developers.html.j2:5
msgid "Taler for developers"
msgstr ""

#: developers.html.j2:12 merchants.html.j2:58
msgid "Free"
msgstr ""

#: developers.html.j2:15
msgid ""
"GNU Taler is free software implementing an open protocol. Anybody is welcome "
"to integrate our reference implementation into their applications. Different "
"components of Taler are being made available under different licenses. The "
"Affero GPLv3+ is used for the exchange, the LGPLv3+ is used for reference "
"code demonstrating integration with merchant platforms, and licenses like "
"GPLv3+ are used for wallets and related customer-facing software. We are "
"open for constructive suggestions for maximizing the adoption of this "
"payment platform."
msgstr ""

#: developers.html.j2:32
msgid "RESTful"
msgstr ""

#: developers.html.j2:35
msgid ""
"Taler is designed to work on the Internet. To ensure that Taler payments can "
"work with restrictive network setups, Taler uses a RESTful protocol over "
"HTTP or HTTPS. Taler's security does not depend upon the use of HTTPS, but "
"obviously merchants may choose to offer HTTPS for consistency and because it "
"generally is better for privacy compared to HTTP. Taler uses JSON to encode "
"structure data, making it easy to integrate Taler with existing Web "
"applications. Taler's protocol is documented in detail at docs.taler.net."
msgstr ""

#: developers.html.j2:58
msgid "Code"
msgstr ""

#: developers.html.j2:61
msgid ""
"Taler is currently primarily developed by a research team at Inria and GNUnet. However, contributions from anyone are welcome. Our Git "
"repositories can be cloned using the Git and HTTP access methods against "
"git.taler.net with the name of the respective repository. A list of "
"repositories can be found in our GitWeb."
msgstr ""

#: developers.html.j2:75
msgid "Documentation"
msgstr ""

#: developers.html.j2:78
msgid ""
"In addition to this website, the documented code and the API "
"documentation. Technical papers can be found in our bibliography."
msgstr ""

#: developers.html.j2:88
msgid "Discussion"
msgstr ""

#: developers.html.j2:91
msgid ""
"We have a mailing list for developer discussions. You can subscribe to or "
"read the list archive at http://lists.gnu.org/mailman/listinfo/taler."
msgstr ""

#: developers.html.j2:101
msgid "Regression Testing"
msgstr ""

#: developers.html.j2:104
msgid ""
"We have Buildbot automation tests to "
"detect regressions and check for portability at buildbot.taler.net."
msgstr ""

#: developers.html.j2:113
msgid "Code Coverage Analysis"
msgstr ""

#: developers.html.j2:116
msgid ""
"We use LCOV to "
"analyze the code coverage of our tests, the results are available at lcov.taler.net."
msgstr ""

#: developers.html.j2:131
msgid "Technical Presentation"
msgstr ""

#: developers.html.j2:134 investors.html.j2:88
msgid "Download"
msgstr ""

#: developers.html.j2:150
msgid "Taler system overview"
msgstr ""

#: developers.html.j2:155
msgid ""
"The Taler system consists of protocols executed among a number of actors as "
"illustrated in the illustration on the right. Typical transactions involve "
"the following steps:"
msgstr ""

#: developers.html.j2:162
msgid "system overview"
msgstr ""

#: developers.html.j2:165
msgid ""
"A customer instructs his bank to transfer funds from his account to "
"the Taler exchange (top left). In the subject of the transaction, he "
"includes an authentication token from his electronic wallet. In Taler "
"terminology, the customer creates a reserve at the exchange."
msgstr ""

#: developers.html.j2:177
msgid ""
"Once the exchange has received the wire transfer, it allows the customer's "
"electronic wallet to withdraw electronic coins. The electronic coins "
"are digital representations of the original currency from the transfer. It "
"is important to note that the exchange does not learn the "serial "
"numbers" of the coins created in this process, so it cannot tell later "
"which customer purchased what at which merchant. The use of Taler does not "
"change the currency or the total value of the funds (except for fees which "
"the exchange may charge for the service)."
msgstr ""

#: developers.html.j2:195
msgid ""
"Once the customer has the digital coins in his wallet, the wallet can be "
"used to spend the coins with merchant portals that support the Taler "
"payment system and accept the respective exchange as a business partner "
"(bottom arrow). This creates a digital contract signed by the customer's "
"coins and the merchant. If necessary, the customer can later use this "
"digitally signed contract in a court of law to prove the exact terms of the "
"contract and that he paid the respective amount. The customer does not learn "
"the banking details of the merchant, and Taler does not require the merchant "
"to learn the identity of the customer. Naturally, the customer can spend any "
"fraction of his digital coins (the system takes care of customers getting "
"change)."
msgstr ""

#: developers.html.j2:217
msgid ""
"Merchants receiving digital coins deposit the respective claims that "
"resulted from the contract signing with the customer at the exchange to "
"redeem the coins. The deposit step does not reveal the details of the "
"contract between the customer and the merchant or the identity of the "
"customer to the exchange in any way. However, the exchange does learn the "
"identity of the merchant via the provided bank routing information. The "
"merchant can, for example when compelled by the state for taxation, provide "
"information linking the individual deposit to the respective contract signed "
"by the customer. Thus, the exchange's database allows the state to enforce "
"that merchants pay applicable taxes (and do not engage in illegal contracts)."
msgstr ""

#: developers.html.j2:240
msgid ""
"Finally, the exchange transfers funds corresponding to the digital coins "
"redeemed by the merchants to the merchant's bank account. The "
"exchange may combine multiple small transactions into one larger bank "
"transfer. The merchant can query the exchange about the relationship between "
"the bank transfers and the individual claims that were deposited."
msgstr ""

#: developers.html.j2:254
msgid ""
"Most importantly, the exchange keeps cryptographic proofs that allow it to "
"demonstrate that it is operating correctly to third parties. The system "
"requires an external auditor, such as a government-appointed "
"financial regulatory body, to frequently verify the exchange's databases and "
"check that its bank balance matches the total value of the remaining coins "
"in circulation."
msgstr ""

#: developers.html.j2:269
msgid ""
"Without the auditor, the exchange operators could embezzle funds they are "
"holding in reserve. Customers and merchants cannot cheat each other or the "
"exchange. If any party's computers are compromised, the financial damage is "
"limited to the respective party and proportional to the funds they have in "
"circulation during the period of the compromise."
msgstr ""

#: faq.html.j2:5
msgid "How is Taler related to Bitcoin or Blockchains?"
msgstr ""

#: faq.html.j2:6
msgid ""
"Taler does not use any Blockchain technology or Bitcoin directly. Taler "
"is not based on proof-of-work or any other distributed consensus mechanism. "
"Instead Taler is based on blind signatures."
msgstr ""

#: faq.html.j2:11
msgid ""
"It would be possible, however, to withdraw coins denominated in Bitcoin "
"into a Taler wallet (with an appropriate exchange), which would give some "
"benefits over plain Bitcoin, such as instant confirmation times."
msgstr ""

#: faq.html.j2:18
msgid "Where is the balance in my wallet stored?"
msgstr ""

#: faq.html.j2:19
msgid ""
"Your wallet stores digital coins and thus ultimately your computer holds "
"your balance. The exchange keeps funds matching all unspent coins in an "
"escrow bank account."
msgstr ""

#: faq.html.j2:25
msgid "What if my wallet is lost?"
msgstr ""

#: faq.html.j2:26
msgid ""
"Since the digital coins of value in your wallet are anonymized, the "
"exchange can not assist you in recovering a lost or stolen wallet. Just like "
"with a physical wallet for cash, you are responsible for keeping it safe."
msgstr ""

#: faq.html.j2:32
msgid ""
"The risk of losing a wallet can be mitigated by making backups or keeping "
"the balance reasonably low."
msgstr ""

#: faq.html.j2:37
msgid "What if my computer is hacked?"
msgstr ""

#: faq.html.j2:38
msgid ""
"In case of a compromise of one of your devices, an attacker can spend "
"coins from your wallet. Checking your balance might reveal to you that your "
"device has been compromised."
msgstr ""

#: faq.html.j2:44
msgid "Can I send money to my friend with Taler?"
msgstr ""

#: faq.html.j2:45
msgid ""
"If your friend provides goods or services for you in exchange for a "
"payment, they can easily set up a Taler merchant and receive the payment in "
"their bank account."
msgstr ""

#: faq.html.j2:50
msgid ""
"Future versions of the Taler wallet may allow exchanging coins among "
"friends directly as well."
msgstr ""

#: faq.html.j2:56
msgid "How does Taler handle payments in different currencies?"
msgstr ""

#: faq.html.j2:57
msgid ""
"Taler wallets can store digital coins corresponding to multiple different "
"currencies such as the Euro, US Dollars or Bitcoins."
msgstr ""

#: faq.html.j2:61
msgid "Taler currently does not offer conversion between currencies."
msgstr ""

#: faq.html.j2:65
msgid "How does Taler protect my privacy?"
msgstr ""

#: faq.html.j2:66
msgid ""
"Your wallet stores digital coins that are blindly signed by an exchange. The use of a "
"blind signature protects your privacy as it prevents the exchange from "
"knowing which coin it signed for which customer."
msgstr ""

#: faq.html.j2:77
msgid "How much does it cost?"
msgstr ""

#: faq.html.j2:78
msgid ""
"The Taler protocol allows any exchange to set its own fee structure, "
"allowing operators to set fees for withdrawing, depositing, refreshing or "
"refunding coins. Operators can also charge fees for closing reserves and for "
"(aggregated) wire transfers to merchants. Merchants may choose to cover some "
"of the fees customers incur. Actual transaction costs are estimated around "
"0.001 cent/transaction (at high transaction rates, amortized over billions "
"of transactions, excluding migration costs). Note that this is an early "
"estimate, details may depend on hosting and backup requirements from the "
"regulator and could thus easily be 10x higher."
msgstr ""

#: faq.html.j2:93
msgid "Does Taler work with international payments?"
msgstr ""

#: faq.html.j2:94
msgid ""
"Taler's wallet supports multiple currencies, but the system currently "
"does not support conversion between currencies. However, in principle an "
"entity that accepts deposits in one currency and allows withdrawals in "
"another currency could be created. Still, the regulatory hurdles in this "
"case tend to be particularly complex. The focus for Taler is on day-to-day "
"payments, so we have no plans to support currency conversion in the near "
"future."
msgstr ""

#: faq.html.j2:107
msgid "How does Taler relate to the (European) Electronic Money Directive?"
msgstr ""

#: faq.html.j2:108
msgid ""
"We believe the European Electronic Money Directive provides part of the "
"regulatory framework a Taler exchange with coins denominated in Euros would "
"have to follow."
msgstr ""

#: faq.html.j2:116
msgid ""
"What bank would guarantee the conversion between Taler coins and bank money "
"in regular bank accounts?"
msgstr ""

#: faq.html.j2:117
msgid ""
"The exchange would be operated by a bank or in cooperation with a bank, "
"and that bank would hold the funds in escrow. Note that this bank could be a "
"regular bank or a central bank for a centrally banked electronic currency. "
"Regardless, the bank would fall under the respective banking regulations "
"establishing a reason why consumers would have faith in the conversion from "
"Taler coins into regular bank money."
msgstr ""

#: faq.html.j2:127
msgid ""
"To whom would consumers complain to in case of non-conversion or non-"
"compliance?"
msgstr ""

#: faq.html.j2:128
msgid ""
"Any exchange should be audited by one or more independent auditors. "
"Merchants and consumer wallets will report certain issues automatically to "
"the auditors, but auditors may also provide a method for manual submission "
"of issues. The auditors are expected to make their reports available to the "
"respective regulatory authorities, or even the general public."
msgstr ""

#: faq.html.j2:138
msgid "Are there any projects already using Taler?"
msgstr ""

#: faq.html.j2:139
msgid ""
"We are aware of several businesses running exploratory projects or having "
"developed working prototypes. We are also in discussions with several "
"regular banks as well as several central banks about the project. That said, "
"there are currently no products in the market yet, and we believe this would "
"be premature given the state of the project (see also our bugtracker for a list of open issues)."
msgstr ""

#: faq.html.j2:151
msgid "Does Taler support recurring payments?"
msgstr ""

#: faq.html.j2:153
msgid ""
"Today, our wallet implementation does not support recurring payments. "
"Recurring payments, where some fixed amount is paid on a regular basis are "
"in theory possible with Taler, but they come with a few caveats. "
"Specifically, recurring payments can only work if the Taler wallet is "
"running and online around the desired time. Furthermore, given their "
"repetitive nature they are linkable, and could thus be used to deanonymize "
"the user making the recurring payment, for example by forcing the user "
"offline at the time of the payment and observing that it does then not "
"happen on time. Finally, the Taler wallet does not work with credit and thus "
"the user would have to make sure to carry a sufficient balance for the "
"recurring payment to be made. Still, they can be useful, and a future "
"version of the Taler wallet will likely support them. But this is not a "
"feature that we are targeting for Taler 1.0. at this time"
msgstr ""

#: features.html.j2:41
msgid "Paying with Taler"
msgstr ""

#: features.html.j2:42
msgid ""
"To pay with Taler, customers install an electronic wallet on their "
"device. Before the first payment, the desired currency must be added to the "
"wallet's balance by some other means of payment.
 Once the wallet is "
"charged, payments on websites take only one click, are never falsely "
"rejected by fraud detection and do not pose any risk of phishing or identity "
"theft.
 Try it yourself with the "
"interactive demo!"
msgstr ""

#: features.html.j2:54
msgid "Receiving payments with Taler"
msgstr ""

#: features.html.j2:55
msgid ""
"To receive Taler payments, a merchant needs a bank account in the desired "
"currency. We provide supporting software in various programming languages to "
"make the integration painless. The merchant's backend for Taler transaction "
"processing can run on the merchant's premises or be hosted by a third party."
"
 Merchant integration is simple, and customers can pay for products "
"without even having to register an account.
 See how merchant integration works in our developer "
"documentation!"
msgstr ""

#: features.html.j2:74
msgid "Practical"
msgstr ""

#: features.html.j2:77
msgid ""
"Taler is easy to integrate with existing Web applications. Payments are "
"cryptographically secured and are confirmed within milliseconds with "
"extremely low transaction costs."
msgstr ""

#: features.html.j2:87
msgid "Stable"
msgstr ""

#: features.html.j2:90
msgid ""
"Taler does not introduce a new currency. Taler uses a digital wallet storing "
"coins and payment service providers with escrow accounts in existing "
"currencies. Thus, Taler's cryptographic coins correspond to existing "
"currencies, such as US Dollars, Euros or even Bitcoins."
msgstr ""

#: features.html.j2:101 governments.html.j2:58 merchants.html.j2:41
msgid "Secure"
msgstr ""

#: features.html.j2:104
msgid ""
"By design Taler does not suffer from many classes of security problems such "
"as phishing or counterfeit. Thanks to its security features, Taler never "
"rejects a legitimate customer due to a fraud-detection false positive."
msgstr ""

#: features.html.j2:116 governments.html.j2:25
msgid "Taxable"
msgstr ""

#: features.html.j2:119
msgid ""
"When using Taler, merchant's revenue is transparent for tax collection "
"authorities. Unlike cash and most digital currencies, Taler helps prevent "
"black markets. Taler is not suitable for illegal activities."
msgstr ""

#: features.html.j2:129
msgid "Private"
msgstr ""

#: features.html.j2:131
msgid ""
"When you pay with Taler, your identity does not have to be revealed. Just "
"like payments in cash, nobody else can track how you spent your electronic "
"money. However, you obtain a legally valid proof of payment."
msgstr ""

#: features.html.j2:142 governments.html.j2:88
msgid "Libre"
msgstr ""

#: features.html.j2:145
msgid ""
"Taler provides protocols and reference implementations that in principle "
"enables anybody to run their own payment infrastructure, be it individuals, "
"organizations or whole countries. Since the reference implementation is a GNU package, it will always remain free "
"software."
msgstr ""

#: financial-news.html.j2:6
msgid "Financial News"
msgstr ""

#: financial-news.html.j2:9
msgid ""
"This page explains (only in English) how Taler can change ongoing "
"developments in the financial industry."
msgstr ""

#: glossary.html.j2:6
msgid "auditor"
msgstr ""

#: glossary.html.j2:8
msgid ""
"trusted third party that verifies that the `exchange` is operating correctly"
msgstr ""

#: glossary.html.j2:12
msgid "bank"
msgstr ""

#: glossary.html.j2:14
msgid ""
"traditional financial service provider who offers wire `transfers` between "
"accounts"
msgstr ""

#: glossary.html.j2:18
msgid "coin"
msgstr ""

#: glossary.html.j2:20
msgid ""
"coins are individual token representing a certain amount of value, also "
"known as the `denomination` of the coin"
msgstr ""

#: glossary.html.j2:24
msgid "contract"
msgstr ""

#: glossary.html.j2:26
msgid "the proposal signed by the wallet."
msgstr ""

#: glossary.html.j2:30
msgid "denomination"
msgstr ""

#: glossary.html.j2:32
msgid ""
"unit of currency, specifies both the currency and the face value of a `coin`"
msgstr ""

#: glossary.html.j2:36
msgid "denomination key"
msgstr ""

#: glossary.html.j2:38
msgid ""
"RSA key used by the exchange to certify that a given `coin` is valid and of "
"a particular `denomination`"
msgstr ""

#: glossary.html.j2:42
msgid "deposit"
msgstr ""

#: glossary.html.j2:44
msgid ""
"operation by which a merchant passes coins to an exchange, expecting the "
"exchange to credit his `bank` account in the future using a wire `transfer`"
msgstr ""

#: glossary.html.j2:48
msgid "dirty"
msgstr ""

#: glossary.html.j2:50
msgid ""
"a `coin` is dirty if its public key may be known to an entity other than the "
"customer, thereby creating the danger of some entity being able to link "
"multiple transactions of coin's owner if the coin is not refreshed first"
msgstr ""

#: glossary.html.j2:54
msgid "exchange"
msgstr ""

#: glossary.html.j2:56
msgid ""
"Taler's payment service provider. Issues electronic `coins` during "
"`withdrawal` and redeems them when they are `deposited` by merchants."
msgstr ""

#: glossary.html.j2:60
msgid "extension"
msgstr ""

#: glossary.html.j2:62
msgid "implementation of a `wallet` for browsers"
msgstr ""

#: glossary.html.j2:66
msgid "fresh coin"
msgstr ""

#: glossary.html.j2:68
msgid "a `coin` is fresh if its public key is only known to the customer"
msgstr ""

#: glossary.html.j2:72
msgid "master key"
msgstr ""

#: glossary.html.j2:74
msgid ""
"offline key used by the exchange to certify denomination keys and message "
"signing keys"
msgstr ""

#: glossary.html.j2:78
msgid "message signing key"
msgstr ""

#: glossary.html.j2:80
msgid "key used by the exchange to sign online messages, other than coins"
msgstr ""

#: glossary.html.j2:84
msgid "offer"
msgstr ""

#: glossary.html.j2:86
msgid ""
"specification of the details of a transaction, specifies the payment "
"obligations for the customer (i.e. the amount), the deliverables of the "
"merchant and other related information, such as deadlines or locations; "
"However, it lacks some information that the backend is supposed to provide. "
"In other words, after the backend adds the missing information to the offer "
"and signs it, it becomes a proposal."
msgstr ""

#: glossary.html.j2:95
msgid "owner"
msgstr ""

#: glossary.html.j2:97
msgid "a `coin` is owned by the entity that knows the private key of the coin"
msgstr ""

#: glossary.html.j2:101
msgid "proof"
msgstr ""

#: glossary.html.j2:103
msgid ""
"message that cryptographically demonstrates that a particular claim is "
"correct"
msgstr ""

#: glossary.html.j2:107
msgid "proposal"
msgstr ""

#: glossary.html.j2:109
msgid "a sketch that has been completed and signed by the merchant backend."
msgstr ""

#: glossary.html.j2:113
msgid "reserve"
msgstr ""

#: glossary.html.j2:115
msgid ""
"funds set aside for future use; either the balance of a customer at the "
"exchange ready for `withdrawal`, or the funds kept in the exchange's bank "
"account to cover obligations from coins in circulation"
msgstr ""

#: glossary.html.j2:119
msgid "refreshing"
msgstr ""

#: glossary.html.j2:121
msgid ""
"operation by which a `dirty` `coin` is converted into one or more `fresh` "
"coins"
msgstr ""

#: glossary.html.j2:125
msgid "refund"
msgstr ""

#: glossary.html.j2:127
msgid ""
"operation by which a merchant steps back from the right to funds that he "
"obtained from a `deposit` operation, giving the right to the funds back to "
"the customer"
msgstr ""

#: glossary.html.j2:131
msgid "sharing"
msgstr ""

#: glossary.html.j2:133
msgid ""
"users can share ownership of a `coin` by sharing access to the coin's "
"private key, thereby allowing all co-owners to spend the coin at any time."
msgstr ""

#: glossary.html.j2:137
msgid "signing key"
msgstr ""

#: glossary.html.j2:139
msgid "see message signing key."
msgstr ""

#: glossary.html.j2:143
msgid "spending"
msgstr ""

#: glossary.html.j2:145
msgid ""
"operation by which a customer gives a merchant the right to `deposit` coins "
"in return for merchandise"
msgstr ""

#: glossary.html.j2:149
msgid "transfer"
msgstr ""

#: glossary.html.j2:151
msgid "method of sending funds between `bank` accounts"
msgstr ""

#: glossary.html.j2:155
msgid "transaction"
msgstr ""

#: glossary.html.j2:157
msgid ""
"method by which ownership is exclusively transferred from one entity to "
"another"
msgstr ""

#: glossary.html.j2:161
msgid "transaction id"
msgstr ""

#: glossary.html.j2:163
msgid "unique number by which a merchant identifies a `transaction`"
msgstr ""

#: glossary.html.j2:167
msgid "wallet"
msgstr ""

#: glossary.html.j2:169
msgid ""
"software running on a customer's computer; withdraws, stores and spends coins"
msgstr ""

#: glossary.html.j2:173
msgid "wire transfer"
msgstr ""

#: glossary.html.j2:175
msgid "see `transfer`"
msgstr ""

#: glossary.html.j2:179
msgid "wire transfer identifier"
msgstr ""

#: glossary.html.j2:181
msgid ""
"subject of a wire `transfer`; usually a random string to uniquely identify "
"the `transfer`"
msgstr ""

#: glossary.html.j2:185
msgid "withdrawal"
msgstr ""

#: glossary.html.j2:187
msgid ""
"operation by which a `wallet` can convert funds from a reserve to fresh coins"
msgstr ""

#: governments.html.j2:6
msgid "Advantages for Governments"
msgstr ""

#: governments.html.j2:8
msgid ""
"Taler provides accountability to ensure business operate legally, while also "
"respecting civil liberties of citizens. Taler is a payment system based on "
"open standards and free software. Taler needs governments as they set a "
"financial framework and act as trusted regulators. Taler contributes to "
"digital sovereignty in the critical financial infrastructure."
msgstr ""

#: governments.html.j2:28
msgid ""
"Taler was built with the goal of fighting corruption and supporting "
"taxation. With Taler, the receiver of any form of payment is easily "
"identified by the government, and the merchant can be compelled to provide "
"the contract that was accepted by the customer. Governments can use this "
"data to tax businesses and individuals based on their income, making tax "
"evasion and black markets less viable."
msgstr ""

#: governments.html.j2:41
msgid ""
"Thus, despite offering anonymity for citizens spending digital cash to buy "
"goods and services, Taler also ensures that the state can observe incoming "
"funds. This can be used to ensure businesses engage only in legal "
"activities, and do not evade income tax, sales tax or value-added tax. "
"However, this observational capability does not extend to the immediate "
"personal domain. In particular, monitoring does not cover shared access to "
"funds with trusted friends and family, or synchronizing wallets across "
"multiple devices."
msgstr ""

#: governments.html.j2:61
msgid ""
"Taler's payments are cryptographically secured. Thus, customers, merchants "
"and the Taler payment service provider (the exchange) can mathematically "
"demonstrate their lawful behavior in court in case of disputes. Financial "
"damages are strictly limited, improving economic security for individuals, "
"merchants, the exchange and the state."
msgstr ""

#: governments.html.j2:73
msgid ""
"As a payment service provider, the Taler exchange is subject to financial "
"regulation. Financial regulation and regular audits are critical to "
"establish trust. In particular, the Taler design mandates the existence of "
"an independent auditor who checks cryptographic proofs that accumulate at "
"the exchange to ensure that the escrow account is managed honestly. This "
"ensures that the exchange does not threaten the economy due to fraud."
msgstr ""

#: governments.html.j2:91
msgid ""
"Taler is free software implementing an open protocol standard. Thus, Taler "
"will enable competition and avoid the monopolization of payment systems that "
"threatens global political and financial stability today."
msgstr ""

#: governments.html.j2:101
msgid "Efficient"
msgstr ""

#: governments.html.j2:104
msgid ""
"Taler has an efficient design. Unlike Blockchain-based payment systems, such "
"as Bitcoin, Taler will not threaten the availability of national electric "
"grids or (significantly) contribute to environmental pollution."
msgstr ""

#: governments.html.j2:120
msgid "Taler and regulation"
msgstr ""

#: governments.html.j2:122
msgid "Anti money laundering (AML)"
msgstr ""

#: governments.html.j2:123
msgid ""
"With Taler, income is visible and can be tied to the contract signed by both "
"parties."
msgstr ""

#: governments.html.j2:124
msgid "Know your customer (KYC)"
msgstr ""

#: governments.html.j2:125
msgid ""
"In Taler, payer and payee are known by their bank accounts when withdrawing "
"or depositing coins respectively"
msgstr ""

#: governments.html.j2:126
msgid "General Data Protection Regulation (GDPR)"
msgstr ""

#: governments.html.j2:127
msgid ""
"Taler cryptographically protects citizen's privacy, and by design implements "
"data minimization and privacy by default."
msgstr ""

#: governments.html.j2:128
msgid "Payment Services Directive (PSD2)"
msgstr ""

#: governments.html.j2:129
msgid ""
"Taler provides an open standard with public APIs contributing to a "
"competitive banking sector."
msgstr ""

#: governments.html.j2:137
msgid "Taler provides privacy and accountability"
msgstr ""

#: governments.html.j2:140
msgid ""
"Taler assumes governments can observe traditional wire transfers entering "
"and leaving the Taler payment system. Starting with the wire transfers, "
"governments can obtain:"
msgstr ""

#: governments.html.j2:148
msgid ""
"The total amount of digital currency withdrawn by a customer. The government "
"can impose limits on how much digital cash a customer can withdraw within a "
"given time frame."
msgstr ""

#: governments.html.j2:157
msgid "The income received by any merchant via the Taler system."
msgstr ""

#: governments.html.j2:164
msgid ""
"The exact details of the underlying contract that was signed between "
"customer and merchant. However, this information would typically not include "
"the identity of the customer."
msgstr ""

#: governments.html.j2:174
msgid ""
"The amounts of digital coins legitimately withdrawn by customers from the "
"exchange, the value of non-redeemed digital coins in customer's wallets, the "
"value and corresponding wire details of deposit operations performed by "
"merchants with the exchange, and the income of the exchange from transaction "
"fees."
msgstr ""

#: gsoc-codeless.html.j2:5
msgid "GSoC 2018: Codeless Payment"
msgstr ""

#: gsoc-codeless.html.j2:6
msgid ""
"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
"guidance of Florian Dold."
msgstr ""

#: gsoc-codeless.html.j2:12
msgid "Overview"
msgstr ""

#: gsoc-codeless.html.j2:14
msgid ""
"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'."
msgstr ""

#: gsoc-codeless.html.j2:23
msgid "Use Cases"
msgstr ""

#: gsoc-codeless.html.j2:24
msgid "The various use cases and features of codeless payment are:"
msgstr ""

#: gsoc-codeless.html.j2:28
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:33
msgid ""
"Merchant has the flexibility to add two types of inventory as follows:  "
"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.
 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).
 "
msgstr ""

#: gsoc-codeless.html.j2:42
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:47
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:53
msgid "Dynamic Merchant Instance"
msgstr ""

#: gsoc-codeless.html.j2:57
msgid "Use Case Diagram"
msgstr ""

#: gsoc-codeless.html.j2:63
msgid "Link to the contributions made"
msgstr ""

#: gsoc-codeless.html.j2:66
msgid "Codeless Payment Backend"
msgstr ""

#: gsoc-codeless.html.j2:68
msgid "Documentation to dynamically manage Merchant Instances"
msgstr ""

#: gsoc-codeless.html.j2:77
msgid "Future Work"
msgstr ""

#: gsoc-codeless.html.j2:79
msgid ""
"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:"
msgstr ""

#: gsoc-codeless.html.j2:84
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:90
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:96
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:102
msgid ""
"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."
msgstr ""

#: gsoc-codeless.html.j2:114
msgid "Screenshots"
msgstr ""

#: index.html.j2:23
msgid ""
"GNU Taler is a payment system that makes privacy-friendly online "
"transactions fast and easy."
msgstr ""

#: investors.html.j2:6
msgid "Invest in Taler!"
msgstr ""

#: investors.html.j2:9
msgid ""
"We have created a company, Taler Systems SA in Luxembourg.
 Please "
"contact invest@taler.net if you want to invest in Taler."
msgstr ""

#: investors.html.j2:24
msgid "The Team"
msgstr ""

#: investors.html.j2:27
msgid ""
"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."
msgstr ""

#: investors.html.j2:37
msgid ""
"We are currently supported by Inria, "
"the French national institute for research in informatics and automation, "
"and the Renewable Freedom "
"Foundation."
msgstr ""

#: investors.html.j2:45
msgid "The Technology"
msgstr ""

#: investors.html.j2:48
msgid ""
"All transactions in Taler are secured using modern cryptography 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."
msgstr ""

#: investors.html.j2:63
msgid "The Business"
msgstr ""

#: investors.html.j2:66
msgid ""
"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."
msgstr ""

#: investors.html.j2:85
msgid "The Business Case"
msgstr ""

#: investors.html.j2:91
msgid ""
"Our financial news page explains in "
"English how Taler can impact current developments in the global payment "
"market."
msgstr ""

#: investors.html.j2:114
msgid "Running a Taler payment service operator"
msgstr ""

#: investors.html.j2:117
msgid ""
"The payment service operator runs the Taler exchange. The exchange "
"charges transaction fees to customers or merchants. Its operational "
"expenses are from wire transfers with the banking system and the operation "
"of the computing infrastructure."
msgstr ""

#: investors.html.j2:127
msgid ""
"Cryptographic operations, bandwidth and storage costs are less than 0.01 "
"cent per transaction."
msgstr ""

#: investors.html.j2:129
msgid ""
"Multiple Taler transactions can be aggregated into larger wire transfers to "
"merchants to minimize wire transfer costs."
msgstr ""

#: investors.html.j2:131
msgid ""
"Protocol allows the exchange to charge fees for any expensive operation "
"(withdraw, deposit, refresh, refund or aggregated wire transfers)."
msgstr ""

#: investors.html.j2:133
msgid "Partnership with banks establishes consumer trust."
msgstr ""

#: investors.html.j2:135
msgid "Partnership with free software community enables rapid deployment."
msgstr ""

#: merchants.html.j2:5
msgid "Advantages for Merchants"
msgstr ""

#: merchants.html.j2:8
msgid ""
"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."
msgstr ""

#: merchants.html.j2:22
msgid "Fast"
msgstr ""

#: merchants.html.j2:25
msgid ""
"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."
msgstr ""

#: merchants.html.j2:44
msgid ""
"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."
msgstr ""

#: merchants.html.j2:61
msgid ""
"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."
msgstr ""

#: merchants.html.j2:76
msgid "Cheap"
msgstr ""

#: merchants.html.j2:79
msgid ""
"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."
msgstr ""

#: merchants.html.j2:89
msgid "Flexible"
msgstr ""

#: merchants.html.j2:92
msgid ""
"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."
msgstr ""

#: merchants.html.j2:101
msgid "Ethical"
msgstr ""

#: merchants.html.j2:104
msgid ""
"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."
msgstr ""

#: merchants.html.j2:119
msgid "Manuals for merchants"
msgstr ""

#: merchants.html.j2:122
msgid "The GNU Taler merchant backend operator manual"
msgstr ""

#: merchants.html.j2:125
msgid "The GNU Taler Web shop integration tutorial (PHP)"
msgstr ""

#: merchants.html.j2:128
msgid "The GNU Taler Web shop integration tutorial (Python)"
msgstr ""

#: merchants.html.j2:140
msgid "The GNU Taler Merchant Backend"
msgstr ""

#: merchants.html.j2:142
msgid "Merchants process payments using the Taler backend:"
msgstr ""

#: merchants.html.j2:147
msgid ""
"The backend signs and stores 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."
msgstr ""

#: merchants.html.j2:156
msgid ""
"The backend validates payments received from the wallet and "
"executes 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."
msgstr ""

#: merchants.html.j2:167
msgid ""
"The backend can list completed transactions and map wire "
"transfers to sets of business transactions, including the exact terms of "
"each contract."
msgstr ""

#: merchants.html.j2:183
msgid "customer perspective"
msgstr ""

#: news.html.j2:16
msgid "More news"
msgstr ""

#: old-news.html.j2:6
msgid "Older News"
msgstr ""

#: old-news.html.j2:9
msgid "This page documents the GNU Taler history."
msgstr ""

#: press.html.j2:4
msgid "GNU Taler in the Press"
msgstr ""

#: schemafuzz.html.j2:6
msgid "SchemaFuzz"
msgstr ""

#: common/base.j2:5
msgid "GNU Taler"
msgstr ""

#: common/base.j2:6
msgid "Taxable Anonymous Libre Electronic Reserves"
msgstr ""

#: common/footer.j2.inc:11
msgid "About"
msgstr ""

#: common/footer.j2.inc:12
msgid "Contact"
msgstr ""

#: common/footer.j2.inc:17
msgid "For Investors"
msgstr ""

#: common/footer.j2.inc:18
msgid "Developer Resources"
msgstr ""

#: common/footer.j2.inc:23
msgid "FAQ"
msgstr ""

#: common/footer.j2.inc:24
msgid "Bibliography"
msgstr ""

#: common/footer.j2.inc:34
msgid ""
"This page was created using Free Software "
"only."
msgstr ""

#: common/navigation.j2.inc:15
msgid "Features"
msgstr ""

#: common/navigation.j2.inc:16
msgid "Design"
msgstr ""

#: common/navigation.j2.inc:17
msgid "Docs"
msgstr ""

#: common/navigation.j2.inc:18
msgid "Team"
msgstr ""