General Developer Manual

20.1. General Developer Manual#

Note

This manual contains information for developers working on GNU Taler and related components. It is not intended for a general audience.

20.1.1. Project Overview#

GNU Taler consists of a large (and growing) number of components in various Git repositories. The following list gives a first overview:

exchange: core payment processing logic with a REST API, plus various helper processes for interaction with banks and cryptographic computations. Also includes the logic for the auditor and an in-memory “bank” API implementation for testing.
libeufin: implementation of the “bank” API using the EBICS protocol used by banks in the EU. Allows an exchange to interact with European banks.
taler-magnet-bank: implementation of the “bank” API using the Magnet Bank API. Allows an exchange to interact with Magnet Bank.
taler-cyclos: implementation of the “bank” API using the Cyclos API. Allows an exchange to interact with a Cyclos network.
taler-wise: implementation of the “bank” API using the Wise API. Allows an exchange to interact with Wise.
depolymerization: implementation of the “bank” API on top of blockchains, specifically Bitcoin and Ethereum. Allows an exchange to interact with crypto-currencies.
merchant: payment processing backend to be run by merchants, offering a REST API.
wallet-core: platform-independent implementation of a wallet to be run by normal users. Includes also the WebExtension for various browsers. Furthermore, includes various single-page apps used by other components (especially as libeufin and merchant). Also includes command-line wallet and tools for testing.
taler-android: Android Apps including the Android wallet, the Android point-of-sale App and the Android casher app.
taler-ios: iOS wallet App.
sync: backup service, provides a simple REST API to allow users to make encrypted backups of their wallet state.
anastasis: key escrow service, provides a simple REST API to allow users to distribute encryption keys across multiple providers and define authorization policies for key recovery.
taler-mdb: integration of Taler with the multi-drop-bus (MDB) API used by vending machines. Allows Taler payments to be integrated with vending machines.
gnu-taler-payment-for-woocommerce: payment plugin for the woocommerce (wordpress) E-commerce solution.
twister: man-in-the-middle proxy for tests that require fuzzing a REST/JSON protocol. Used for some of our testing.
challenger: implementation of an OAuth 2.0 provider that can be used to verify that a user can receive SMS or E-mail at particular addresses. Used as part of KYC processes of the exchange.
taler-mailbox: messaging service used to store and forward payment messages to Taler wallets.
taldir: directory service used to lookup Taler wallet addresses for sending invoices or payments to other wallets.
taler-merchant-demos: various demonstration services operated at ‘demo.taler.net’, including a simple shop and a donation page.

There are other important repositories without code, including:

gana: Hosted on git.gnunet.org, this repository defines various constants used in the GNU Taler project.
docs: documentation, including this very document.
marketing: various presentations, papers and other resources for outreach.
large-media: very large data objects, such as videos.
www: the taler.net website.

20.1.2. Fundamentals#

20.1.2.1. Versioning#

A central rule is to never break anything for any dependency. To accomplish this, we use versioning, of the APIs, database schema and the protocol. The database versioning approach is described in the Database schema versioning section. Here, we will focus on API and protocol versioning.

The key issue we need to solve with protocols and APIs (and that does not apply to database versioning) is being able to introduce and remove features without requiring a flag day where all components must update at the same time. For this, we use GNU libtool style versioning with MAJOR:REVISION:AGE and not semantic versioning (SEMVER). With GNU libtool style versioning, first the REVISION should be increased on every change to the respective code. Then, each time a feature is introduced or deprecated, the MAJOR and AGE numbers are increased. Whenever an API is actually removed the AGE number is reduced to match the distance since the removed API was deprecated. Thus, if some client implements version X of the protocol (including not using any APIs that have been deprecated), it is compatible for any implementation where MAJOR is larger or equal to X, and MAJOR minus AGE is smaller or equal to X. REVISION is not used for expected compatibility issues and merely serves to uniquely identify each version (in combination with MAJOR).

To evolve any implementation, it is thus critical to first of all never just break an existing API or endpoint. The only acceptable modifications are to return additional information (being aware of binary compatibility!) or to accept additional optional arguments (again, in a way that does not break existing users). Thus, the most common way to introduce changes will be the addition of new endpoints. Breaking existing endpoints is only ever at best acceptable while in the process of introducing it and if you are absolutely sure that there are zero users in other components.

When removing endpoints (or fields being returned), you must first deprecate the existing API (incrementing MAJOR and AGE) and then wait for all clients, including all clients in operation (e.g. Android and iOS Apps, e-commerce integrations, etc.) to upgrade to a protocol implementation above the deprecated MAJOR revision. Only then you should remove the endpoint and reduce AGE.

To document these changes, please try to use @since annotations in the API specifications to explain the MAJOR revision when a feature became available, but most importantly use @deprecated X annotations to indicate that an API was deprecated and will be removed once MAJOR minus AGE is above X. When using an API, use the /config endpoints to check for compatibility and show a warning if the version(s) you support and the version(s) offered by the server are incompatible.

20.1.2.2. Tagging and Package Versioning#

Release tags are of the form v${major}.${minor}.${patch}. Release tags should be annotated git tags.

We usually consider Debian packaging files (in debian/) to be part of a release. When only the Debian packaging files need to be changed, there are two options:

Make a new patch release (v${major}.${minor}.${patch+1})
Make a Debian release:
- Debian version now includes a revision: ${major}.${minor}.${patch}-${debrevision}
- The tag is Debian-specific: debian-${major}.${minor}.${patch}-${debrevision}

All source repos should include a contrib/bump script that automates bumping theversion in all relevant source and packaging files. In the future, we might add an option to the script to only release a packaging bump. Right now, that process is manual.

We support tagged and published pre-release versions via tags of the form v${major}.${minor}.${patch}-dev.${n}. The corresponding Debian version must be ${major}.${minor}.${patch}~dev${n}.

Nightly Debian packages should follow the Debian conventions of {upcoming_version}~git{date}.{hash}-{revision}.

20.1.2.3. Testing Tools#

For full make check support, install these programs:

The make check should be able to function without them, but their presence permits some tests to run that would otherwise be skipped.

20.1.2.4. Manual Testing Database Reset#

Sometimes make check will fail with some kind of database (SQL) error, perhaps with a message like OBJECT does not exist in the test-suite.log file, where OBJECT is the name of a table or function. In that case, it may be necessary to reset the talercheck database with the commands:

$ dropdb talercheck
$ createdb talercheck

This is because, at the moment, there is no support for doing these steps automatically in the make check flow.

(If make check still fails after the reset, file a bug report as usual.)

20.1.2.5. Bug Tracking#

Bug tracking is done with Mantis (https://www.mantisbt.org/). The bug tracker is available at https://bugs.taler.net. A registration on the Web site is needed in order to use the bug tracker, only read access is granted without a login.

We use the following conventions for the bug states:

NEW: Incoming bugs are in ‘new’ so that management (or developers) can easily identify those that need to be checked (report correct? something we want to fix?), prioritized and targeted for releases. “NEW” bugs are never assigned to a developer.
FEEDBACK: When blocked on feedback from reporter or other developer. Assigned to other developer (but cannot be assigned to reporter, in this case MAY remain associated with the developer who expects the feedback). If a bug is on feedback, it automatically should be considered to be high-priority to give the feedback (as it is blocking someone else!).
ACKNOWLEDGED: The bug has been reviewed, but no decision about what action to take has been made yet. Should not be worked on until management (or a developer) comes up with a plan. “ACKNOWLEDGED” bugs should NOT be assigned to a developer.
CONFIRMED: This is a real issue that should be worked on, but is not yet actively worked on. If working on this bug requires other bugs to be fixed first, they should be added as child-bugs (via relationships). Developers are always welcome to self-assign bugs that are “CONFIRMED” if they start to work on a bug. “CONFIRMED” bugs should NOT be assigned to a developer.
ASSIGNED: The specific developer the bug is assigned to is actively working on the issue. Developers should strive to not have more than 5-10 bugs assigned to them at any time. Only having one assigned to you is totally OK! Developers should aggressively un-assign bugs that they are blocked on, cannot make progress on, or are no longer actively working on (but of course, better resolve them before moving on if possible). If the bug remains open, it probably should go back to “CONFIRMED” or “ACKNOWLEDGED”.
RESOLVED: The bug has been fixed in Git.
CLOSED: An official release was made with the fix in it.

When developers want to keep an eye on certain bugs, they should monitor them. Multiple developers can be monitoring a bug, but it can only be assigned to one. Developers should also keep an eye on the roadmap (by release), bug categories they care about, and of course priorities / severities.

We use tags to categorize bugs. Common tags that also imply some urgency include (in alphabetical order):

accounting: issues required for accounting (such as taxes by merchants)
compliance: issues related to regulatory compliance
$CUSTOMER: issues requested by a particular customer
performance: performance problems or ideas for improvement
security: security issues (including planned improvements to security)
UX: user experience issues

These tags should be attached to “NEW” bugs if they apply.

20.1.2.6. Code Repositories#

Taler code is versioned with Git. For those users without write access, all the codebases are found at the following URL:

git://git.taler.net/<repository>

A complete list of all the existing repositories is currently found at https://git.taler.net/.

20.1.2.7. Committing code#

Before you can obtain Git write access, you must sign the copyright agreement. As we collaborate closely with GNUnet, we use their copyright agreement – with the understanding that your contributions to GNU Taler are included in the assignment. You can find the agreement on the GNUnet site. Please sign and mail it to Christian Grothoff as he currently collects all the documents for GNUnet e.V.

To obtain Git access, you need to send us your SSH public key. Most core team members have administrative Git access, so simply contact whoever is your primary point of contact so far. You can find instructions on how to generate an SSH key in the Git book. If you have been granted write access, you first of all must change the URL of the respective repository to:

ssh://git@git.taler.net/<repository>

For an existing checkout, this can be done by editing the .git/config file.

The server is configured to reject all commits that have not been signed with GnuPG. If you do not yet have a GnuPG key, you must create one, as explained in the GNU Privacy Handbook. You do not need to share the respective public key with us to make commits. However, we recommend that you upload it to key servers, put it on your business card and personally meet with other GNU hackers to have it signed such that others can verify your commits later.

To sign all commits, you should run

$ git config --global commit.gpgsign true

You can also sign individual commits only by adding the -S option to the git commit command. If you accidentally already made commits but forgot to sign them, you can retroactively add signatures using:

$ git rebase -S

Whether you commit to a personal branch (recommended: dev/$USER/...), a feature branch or to master should depend on your level of comfort and the nature of the change. As a general rule, the code in master must always build and tests should always pass, at least on your own system. However, we all make mistakes and you should expect to receive friendly reminders if your change did not live up to this simple standard. We plan to move to a system where the CI guarantees this invariant in the future.

In order to keep a linear and clean commits history, we advise to avoid merge commits and instead always rebase your changes before pushing to the master branch. If you commit and later find out that new commits were pushed, the following command will pull the new commits and rebase yours on top of them.

# -S instructs Git to (re)sign your commits
$ git pull --rebase -S

20.1.2.8. Observing changes#

Every commit to the master branch of any of our public repositories (and almost all are public) is automatically sent to the gnunet-svn@gnu.org mailinglist. That list is for Git commits only, and must not be used for discussions. It also carries commits from our main dependencies, namely GNUnet and GNU libmicrohttpd. While it can be high volume, the lists is a good way to follow overall development.

20.1.2.9. Code generator usage policy#

We do neither encourage nor discourage the use of tools for code generation. It is up to the individual developer to decide if a tool is acceptable for a particular task. But of course, we do encourage you to use FLOSS tools and we MUST NOT become dependent on non-free software! That said, if you use tools, you must document their use and in particular satisfy the NLnet policy on the use of “AI”.

Specifically, we ask developers to always put generated code into a separate Git commit and to include the full prompt in the commit message. Naturally, you may clean up the code generator’s output, but then you should do so in separate Git commits (and of course only merge into master/stable after the clean up is complete). But do preserve (not squash!) the commit with the generated code so that it remains documented what the prompts were and which code is generated. This will go a long way to keep code auditors sane!

20.1.2.10. Communication#

For public discussions we use the taler@gnu.org mailinglist. All developers should subscribe to the low-volume Taler mailinglist. There are separate low-volume mailinglists for gnunet-developers (@gnu.org) and for libmicrohttpd (@gnu.org). For internal discussions we use https://mattermost.taler.net/ (invitation only, but also archived).

20.1.2.11. What to put in bootstrap#

Each repository has a bootstrap script, which contains commands for the developer to run after a repository checkout (i.e., after git clone or git pull). Typically, this updates and initializes submodules, prepares the tool chain, and runs autoreconf. The last step generates the configure script, whether for immediate use or for inclusion in the distribution tarball.

One common submodule is contrib/gana, which pulls from the GNUnet GANA repository. For example, in the Taler exchange repository, the bootstrap script eventually runs the git submodule update --init command early on, and later runs script ./contrib/gana-generate.sh, which generates files such as src/include/taler_signatures.h.

Thus, to update that file, you need to:

(in GANA repo) Find a suitable (unused) name and number for the Signature Purposes database.
Add it to GANA, in gnunet-signatures/registry.rec. (You can check for uniqueness with the recfix utility.)
Commit the change, and push it to the GANA Git repo.
(in Taler Repo) Run the contrib/gana-latest.sh script.
Bootstrap, configure, do make install, make check, etc. (Basically, make sure the change does not break anything.)
Commit the submodule change, and push it to the Taler exchange Git repo.

A similar procedure is required for other databases in GANA. See file README in the various directories for specific instructions.

20.1.3. Debian and Ubuntu Repositories#

We package our software for Debian and Ubuntu.

20.1.3.1. Nightly Repositories#

To try the latest, unstable and untested versions of packages, you can add the nightly package sources.

# For Debian (trixie)
$ curl -sS https://deb.taler.net/apt-nightly/taler-trixie-ci.sources \
  | tee /etc/apt/sources.list.d/taler-trixie-nightly.sources

20.1.4. Taler Deployment on gv.taler.net#

This section describes the GNU Taler deployment on gv.taler.net. gv is our server at BFH. It hosts the Git repositories, Web sites, CI and other services. Developers can receive an SSH account and e-mail alias for the system, you should contact Javier, Christian or Florian. As with Git, ask your primary team contact for shell access if you think you need it.

20.1.4.1. DNS#

DNS records for taler.net are controlled by the GNU Taler maintainers, specifically Christian and Florian, and our system administrator, Javier. If you need a sub-domain to be added, please contact one of them.

20.1.4.2. User Acccounts#

On gv.taler.net, there are three system users that are set up to serve Taler on the Internet:

head: serves *.head.taler.net and gets automatically built by Buildbot every 2 hours from the sandcastle-ng.git. Master key may be reset occasionally
taler-test: serves *.test.taler.net and does NOT get automatically built, and runs more recent tags and/or unreleased versions of Taler components. Master key may be reset occasionally.
demo: serves *.demo.taler.net. Never automatically built. Master key is retained.

20.1.5. Demo Upgrade Procedure#

Login as the demo user on gv.taler.net.
Pull the latest sandcastle-ng.git code in checkout at $HOME/sandcastle-ng.
Run systemctl --user restart container-taler-sandcastle-demo.service
Refer to the sandcastle-ng README (https://git.taler.net/sandcastle-ng.git/about/) for more info.

Upgrading the demo environment should be done with care, and ideally be coordinated on the mailing list before. It is our goal for demo to always run a “working version” that is compatible with various published wallets. Please use the demo upgrade checklist to make sure everything is working. Nginx is already configured to reach the services as exported by the user unit.

20.1.5.1. Tagging components#

All Taler components must be tagged with git before they are deployed on the demo environment, using a tag of the following form:

demo-YYYY-MM-DD-SS
YYYY = year
MM = month
DD = day
SS = serial

20.1.6. Environments and Builders on taler.net#

20.1.6.1. Buildbot implementation#

GNU Taler uses a buildbot implementation (front end at https://buildbot.taler.net) to manage continuous integration. Buildbot documentation is at https://docs.buildbot.net/.

Here are some highlights:

The WORKER is the config that that lives on a shell account on a localhost (taler.net), where this host has buildbot-worker installed. The WORKER executes the commands that perform all end-functions of buildbot.
The WORKER running buildbot-worker receives these commands by authenticating and communicating with the buildbot server using parameters that were specified when the worker was created in that shell account with the buildbot-worker command.
The buildbot server’s master.cfg file contains FACTORY declarations which specify the commands that the WORKER will run on localhost.
The FACTORY is tied to the WORKER in master.cfg by a BUILDER.
The master.cfg also allows for SCHEDULER that defines how and when the BUILDER is executed.
Our master.cfg file is checked into git, and then periodically updated on a particular account on taler.net (ask Christian for access if needed). Do not edit this file directly/locally on taler.net, but check changes into Git.

Best Practices:

When creating a new WORKER in the master.cfg file, leave a comment specifying the server and user account that this WORKER is called from. (At this time, taler.net is the only server used by this implementation, but it’s still good practice.)
Create a worker from a shell account with this command: buildbot-worker create-worker <workername> localhost <username> <password>

Then make sure there is a WORKER defined in master.cfg like: worker.Worker("<username>", "<password>")

20.1.6.2. Test builder#

This builder (test-builder) compiles and starts every Taler component. The associated worker is run by the taler-test Gv user, via the SystemD unit buildbot-worker-taler. The following commands start/stop/restart the worker:

systemctl --user start buildbot-worker-taler
systemctl --user stop buildbot-worker-taler
systemctl --user restart buildbot-worker-taler

Note

the mentioned unit file can be found at deployment.git/systemd-services/

20.1.6.3. Wallet builder#

This builder (wallet-builder) compiles every Taler component and runs the wallet integration tests. The associated worker is run by the walletbuilder Gv user, via the SystemD unit buildbot-worker-wallet. The following commands start/stop/restart the worker:

systemctl --user start buildbot-worker-wallet
systemctl --user stop buildbot-worker-wallet
systemctl --user restart buildbot-worker-wallet

Note

the mentioned unit file can be found at deployment.git/systemd-services/

20.1.6.4. Documentation Builder#

All the Taler documentation is built by the user docbuilder that runs a Buildbot worker. The following commands set the docbuilder up, starting with an empty home directory.

# Log-in as the 'docbuilder' user.

$ cd $HOME
$ git clone git://git.taler.net/deployment
$ ./deployment/bootstrap-docbuilder

# If the previous step worked, the setup is
# complete and the Buildbot worker can be started.

$ buildbot-worker start worker/

20.1.6.5. Website Builder#

Taler Websites, www.taler.net and stage.taler.net, are built by the user taler-websites by the means of a Buildbot worker. The following commands set the taler-websites up, starting with an empty home directory.

# Log-in as the 'taler-websites' user.

$ cd $HOME
$ git clone git://git.taler.net/deployment
$ ./deployment/bootstrap-sitesbuilder

# If the previous step worked, the setup is
# complete and the Buildbot worker can be started.

$ buildbot-worker start worker/

20.1.6.6. Code coverage#

Code coverage tests are run by the lcovworker user, and are also driven by Buildbot.

# Log-in as the 'lcovworker' user.

$ cd $HOME
$ git clone git://git.taler.net/deployment
$ ./deployment/bootstrap-taler lcov

# If the previous step worked, the setup is
# complete and the Buildbot worker can be started.

$ buildbot-worker start worker/

The results are then published at https://lcov.taler.net/.

20.1.6.7. Producing auditor reports#

Both ‘test’ and ‘demo’ setups get their auditor reports compiled by a Buildbot worker. The following steps get the reports compiler prepared.

# Log-in as <env>-auditor, with <env> being either 'test' or 'demo'

$ git clone git://git.taler.net/deployment
$ ./deployment/buildbot/bootstrap-scripts/prepare-auditorreporter <env>

# If the previous steps worked, then it should suffice to start
# the worker, with:

$ buildbot-worker start worker/

20.1.6.8. Database schema versioning#

The PostgreSQL databases of the exchange and the auditor are versioned. See the versioning.sql file in the respective directory for documentation.

Every set of changes to the database schema must be stored in a new versioned SQL script. The scripts must have contiguous numbers. After any release (or version being deployed to a production or staging environment), existing scripts MUST be immutable.

Developers and operators MUST NOT make changes to database schema outside of this versioning. All tables of a GNU Taler component should live in their own schema.

20.1.7. QA Plans#

20.1.7.1. Taler 1.0 QA Plan#

20.1.7.1.1. Wallet Platforms#

Platforms listed here are the officially supported platforms for this release.

Overview / Installation Page
- https://taler.net/en/wallet.html aka https://wallet.taler.net/
Android
- Google Play: https://play.google.com/store/apps/details?id=net.taler.wallet
- F-Droid: https://f-droid.org/en/packages/net.taler.wallet.fdroid/
- APK Download: https://taler.net/files/wallet/wallet-latest.apk (does not yet exist!)
Browser
- Chrome: https://chromewebstore.google.com/detail/gnu-taler-wallet/millncjiddlpgdmkklmhfadpacifaonc
- Firefox: https://addons.mozilla.org/en-US/firefox/addon/taler-wallet/
iOS

20.1.7.1.2. Running Deployments#

These deployments should work for the release:

Sandcastle-based:
- demo.taler.net
- test.taler.net
- head.taler.net
Regio-based:
- regio-taler.fdold.eu
- exchange.e.netzbon-basel.ch (requires external help!)
- Klima-Taler (requires external help!)
Custom:
- exchange.chf.taler.net (BFH)!
Ansible-based:
- exchange.taler-ops.ch

20.1.7.1.3. Check UX Flows#

See the demo upgrade checklist.

20.1.7.1.4. Regio Deployment#

Deployment Automation (deployment.git/regional-currency)
- Test with Debian bookworm
- Test with Ubuntu noble
- Check logs for errors
- Test with telesign (SMS)
- Set up EBICS integration
- Check that ToS is configured
Deployment Functionality
- All flows of the wallet should work (see Wallet Flows above)
- All flows of libeufin-bank should work (see libeufin-bank Flows above)
- Merchant backend should work (see Merchant Backend SPA Flows above)
- Check logs

20.1.7.1.5. Continuous Integration#

https://buildbot.taler.net/#/waterfall
CI should pass

20.1.7.1.6. Debian Repository#

Debian
- repo at https://deb.taler.net/apt/debian/
- supported codename(s): bookworm
Ubuntu:
- repo at https://deb.taler.net/apt/ubuntu/
- supported codename(s): noble

20.1.7.1.7. GNU Release#

Release announcement
FTP upload

20.1.9. Continuous integration#

CI is done with Buildbot (https://buildbot.net/), and builds are triggered by the means of Git hooks. The results are published at https://buildbot.taler.net/ .

In order to avoid downtimes, CI uses a “blue/green” deployment technique. In detail, there are two users building code on the system, the “green” and the “blue” user; and at any given time, one is running Taler services and the other one is either building the code or waiting for that.

There is also the possibility to trigger builds manually, but this is only reserved to “admin” users.

20.1.10. Internationalisation#

Internationalisation (a.k.a “translation”) is handled using text-based localization files named PO (Portable Object) holding pairs of original and translated strings.

Preferred translations of GNU Taler user-facing terminology across supported locales. Each entry lists the English source term followed by the agreed translation for every locale that has one; the Notes field records rationale and disambiguation guidance.

wallet

Arabic:: محفظة
Catalan:: cartera
Czech:: peněženka
German:: Wallet
Greek:: πορτοφόλι
Spanish:: cartera
Finnish:: lompakko
French:: portefeuille numérique
Friulian:: tacuin
Galician:: carteira
Hebrew:: ארנק
Hindi:: wallet
Hungarian:: pénztárca
Italian:: portafoglio
Japanese:: ウォレット
Korean:: 지갑
Dutch:: portemonnee
Polish:: portfel
Portuguese:: carteira
Portuguese (Brazil):: carteira
Russian:: кошелёк
Slovak:: peňaženka
Swedish:: plånbok
Turkish:: cüzdan
Ukrainian:: гаманець
Chinese (Simplified):: 钱包
Chinese (Traditional):: 錢包
Notes:: App holding digital cash; use the native purse/wallet word, not bank-account sense

exchange

Arabic:: الصرافة
Catalan:: Proveïdor de canvi
Czech:: Exchange
German:: Exchange
Greek:: Exchange
Spanish:: exchange
Finnish:: Exchange
French:: exchange
Friulian:: Exchange
Galician:: exchange
Hebrew:: חלפן
Hindi:: एक्सचेंज
Hungarian:: exchange
Italian:: Exchange
Japanese:: 取引所
Korean:: 거래소
Dutch:: exchange
Polish:: Exchange
Portuguese:: Exchange
Portuguese (Brazil):: câmbio
Russian:: обменник
Slovak:: Exchange
Swedish:: Exchange
Turkish:: exchange
Ukrainian:: Exchange
Chinese (Simplified):: 交易所
Chinese (Traditional):: 交易所
Notes:: Taler service converting bank money<->coins; keep “Exchange” as a proper noun where a local word (stock/bureau de change) would mislead; sv keeps ‘Exchange’ (proper noun) — ‘växlingskontor’ misleads as bureau-de-change

merchant

Arabic:: التاجر
Catalan:: Comerciant
Czech:: obchodník
German:: Händler
Greek:: έμπορος
Spanish:: comerciante
Finnish:: kauppias
French:: commerçant
Friulian:: marcjadant
Galician:: comerciante
Hebrew:: סוחר
Hindi:: व्यापारी
Hungarian:: kereskedő
Italian:: venditore
Japanese:: マーチャント
Korean:: 상인
Dutch:: verkoper
Polish:: sprzedawca
Portuguese:: comerciante
Portuguese (Brazil):: comerciante
Russian:: продавец
Slovak:: obchodník
Swedish:: säljare
Turkish:: satıcı
Ukrainian:: продавець
Chinese (Simplified):: 商户
Chinese (Traditional):: 商家
Notes:: Seller accepting Taler (commerce sense), not generic trader/dealer

payment

Arabic:: الدفع
Catalan:: Pagament
Czech:: platba
German:: Zahlung
Greek:: πληρωμή
Spanish:: pago
Finnish:: maksu
French:: paiement
Friulian:: paiament
Galician:: pago
Hebrew:: תשלום
Hindi:: भुगतान
Hungarian:: fizetés
Italian:: pagamento
Japanese:: 支払い
Korean:: 결제
Dutch:: betaling
Polish:: płatność
Portuguese:: pagamento
Portuguese (Brazil):: pagamento
Russian:: платёж · оплата
Slovak:: platba
Swedish:: betalning
Turkish:: ödeme
Ukrainian:: платіж
Chinese (Simplified):: 支付
Chinese (Traditional):: 付款
Notes:: Act of paying / a payment instance | ru split: платёж=payment instance, оплата=act/process of paying

withdraw

Arabic:: سحب
Catalan:: Retirar
Czech:: výběr
German:: abheben
Greek:: ανάληψη
Spanish:: retirar
Finnish:: nostaa
French:: retirer
Friulian:: prelevâ
Galician:: retirar
Hebrew:: משיכה
Hindi:: निकासी
Hungarian:: felvenni
Italian:: prelevare
Japanese:: 引き出し
Korean:: 출금
Dutch:: opnemen
Polish:: wypłacić
Portuguese:: levantar
Portuguese (Brazil):: retirar
Russian:: снятие
Slovak:: výber
Swedish:: ta ut
Turkish:: çekmek
Ukrainian:: зняття
Chinese (Simplified):: 提取
Chinese (Traditional):: 提取
Notes:: Take digital cash out of the exchange into the wallet (banking withdrawal sense)

deposit

Arabic:: إيداع
Catalan:: Dipòsit
Czech:: vklad
German:: Einzahlung
Greek:: κατάθεση
Spanish:: depósito
Finnish:: talletus
French:: dépôt
Friulian:: dipuesit
Galician:: depósito
Hebrew:: הפקדה
Hindi:: जमा
Hungarian:: befizetés
Italian:: deposito
Japanese:: 預け入れ
Korean:: 입금
Dutch:: storten
Polish:: depozyt
Portuguese:: depósito
Portuguese (Brazil):: depósito
Russian:: депонирование
Slovak:: vklad
Swedish:: insättning
Turkish:: yatırma
Ukrainian:: депозит
Chinese (Simplified):: 存款
Chinese (Traditional):: 存款
Notes:: Merchant submits coins to the exchange for credit (banking deposit sense)

bank

Arabic:: البنك
Czech:: banka
German:: Bank
Greek:: τράπεζα
Spanish:: banco
Finnish:: pankki
French:: banque
Friulian:: bancje
Galician:: banco
Hebrew:: בנק
Hindi:: बैंक
Hungarian:: bank
Italian:: banca
Japanese:: 銀行
Korean:: 은행
Dutch:: bank
Polish:: bank
Portuguese:: banco
Portuguese (Brazil):: banco
Russian:: банк
Slovak:: banka
Swedish:: bank
Turkish:: banka
Ukrainian:: банк
Chinese (Simplified):: 银行
Chinese (Traditional):: 銀行

transaction

Arabic:: معاملة
Czech:: transakce
German:: Transaktion
Greek:: συναλλαγή
Spanish:: transacción
Finnish:: transaktio
French:: transaction
Friulian:: transazion
Galician:: transacción
Hebrew:: עסקה
Hindi:: लेन-देन
Hungarian:: tranzakció
Italian:: transazione
Japanese:: 取引
Korean:: 거래
Dutch:: transactie
Polish:: transakcja
Portuguese:: transação
Portuguese (Brazil):: transação
Russian:: транзакция
Slovak:: transakcia
Swedish:: transaktion
Turkish:: işlem
Ukrainian:: транзакція
Chinese (Simplified):: 交易
Chinese (Traditional):: 交易

currency

Arabic:: عملة
Catalan:: Divisa
Czech:: měna
German:: Währung
Greek:: νόμισμα
Spanish:: divisa
Finnish:: valuutta
French:: monnaie · devise
Friulian:: valude
Galician:: moeda
Hebrew:: מטבע
Hindi:: मुद्रा
Hungarian:: valuta
Italian:: valuta
Japanese:: 通貨
Korean:: 통화
Dutch:: valuta
Polish:: waluta
Portuguese:: moeda
Portuguese (Brazil):: moeda
Russian:: валюта
Slovak:: mena
Swedish:: valuta
Turkish:: para birimi
Ukrainian:: валюта
Chinese (Simplified):: 货币
Chinese (Traditional):: 貨幣
Notes:: Monetary system/unit; distinct from a single “coin” | fr split: monnaie=general money, devise=foreign/FX currency

coin

Arabic:: عملة معدنية
Czech:: mince
German:: Münze
Greek:: κέρμα
Spanish:: moneda
Finnish:: kolikko
French:: pièce
Friulian:: monede
Galician:: moeda
Hebrew:: מטבע
Hindi:: सिक्का
Hungarian:: érme
Italian:: moneta
Japanese:: コイン
Korean:: 코인
Dutch:: munt
Polish:: moneta
Portuguese:: moeda
Portuguese (Brazil):: moeda
Russian:: монета
Slovak:: minca
Swedish:: mynt
Turkish:: para
Ukrainian:: монета
Chinese (Simplified):: 币
Chinese (Traditional):: 硬幣
Notes:: An individual digital token of value

fee

Arabic:: رسوم
Catalan:: Comissió
Czech:: poplatek
German:: Gebühr
Greek:: προμήθεια
Spanish:: comisión
Finnish:: maksu
French:: frais
Friulian:: comission
Galician:: comisión
Hebrew:: עמלה
Hindi:: शुल्क
Hungarian:: díj
Italian:: commissione
Japanese:: 手数料
Korean:: 수수료
Dutch:: kosten
Polish:: opłata
Portuguese:: taxa
Portuguese (Brazil):: taxa
Russian:: комиссия
Slovak:: poplatok
Swedish:: avgift
Turkish:: ücret
Ukrainian:: комісія
Chinese (Simplified):: 费用
Chinese (Traditional):: 費用
Notes:: Charge levied by an operator

escrow

Arabic:: ضمان
Czech:: úschova
German:: Treuhand
Greek:: μεσεγγύηση
Spanish:: depósito de garantía
Finnish:: sulkutili
French:: compte séquestre
Friulian:: cont di garanzie
Galician:: custodia
Hebrew:: נאמנות
Hindi:: एस्क्रो
Hungarian:: letét
Italian:: garanzia
Japanese:: エスクロー
Korean:: 에스크로
Dutch:: escrow
Polish:: rachunek powierniczy
Portuguese:: custódia
Portuguese (Brazil):: custódia
Russian:: эскроу
Slovak:: viazaný účet
Swedish:: deposition
Turkish:: emanet
Ukrainian:: ескроу
Chinese (Simplified):: 托管
Chinese (Traditional):: 託管
Notes:: Funds held in trust on behalf of others

backup

Arabic:: نسخ احتياطي
Czech:: záloha
German:: Sicherung
Greek:: αντίγραφο ασφαλείας
Spanish:: copia de seguridad
Finnish:: varmuuskopio
French:: sauvegarde
Friulian:: backup
Galician:: copia de seguridade
Hebrew:: גיבוי
Hindi:: बैकअप
Hungarian:: biztonsági mentés
Italian:: backup
Japanese:: バックアップ
Korean:: 백업
Dutch:: back-up
Polish:: kopia zapasowa
Portuguese:: cópia de segurança
Portuguese (Brazil):: backup
Russian:: резервное копирование
Slovak:: záloha
Swedish:: säkerhetskopiering
Turkish:: yedekleme
Ukrainian:: резервне копіювання
Chinese (Simplified):: 备份
Chinese (Traditional):: 備份

recovery

Arabic:: استعادة
Czech:: obnova
German:: Wiederherstellung
Greek:: ανάκτηση
Spanish:: recuperación
Finnish:: palautus
French:: récupération
Friulian:: recupero
Galician:: recuperación
Hebrew:: שחזור
Hindi:: पुनर्प्राप्ति
Hungarian:: helyreállítás
Italian:: recupero
Japanese:: 復旧
Korean:: 복구
Dutch:: herstel
Polish:: odzyskiwanie
Portuguese:: recuperação
Portuguese (Brazil):: recuperação
Russian:: восстановление
Slovak:: obnova
Swedish:: återställning
Turkish:: kurtarma
Ukrainian:: відновлення
Chinese (Simplified):: 恢复
Chinese (Traditional):: 復原

auditor

Arabic:: مدقق
Czech:: auditor
German:: Auditor
Greek:: ελεγκτής
Spanish:: auditor
Finnish:: tilintarkastaja
French:: auditeur
Friulian:: revisôr
Galician:: auditor
Hebrew:: מבקר
Hindi:: लेखा परीक्षक
Hungarian:: auditor
Italian:: revisore
Japanese:: 監査
Korean:: 감사인
Dutch:: auditor
Polish:: audytor
Portuguese:: auditor
Portuguese (Brazil):: auditor
Russian:: аудитор
Slovak:: audítor
Swedish:: revisor
Turkish:: denetçi
Ukrainian:: аудитор
Chinese (Simplified):: 审计
Chinese (Traditional):: 審計員

contract

Arabic:: عقد
Czech:: smlouva
German:: Vertrag
Greek:: σύμβαση
Spanish:: contrato
Finnish:: sopimus
French:: contrat
Friulian:: contrat
Galician:: contrato
Hebrew:: חוזה
Hindi:: अनुबंध
Hungarian:: szerződés
Italian:: contratto
Japanese:: 契約
Korean:: 계약
Dutch:: contract
Polish:: umowa
Portuguese:: contrato
Portuguese (Brazil):: contrato
Russian:: договор
Slovak:: zmluva
Swedish:: kontrakt
Turkish:: sözleşme
Ukrainian:: договір
Chinese (Simplified):: 合同
Chinese (Traditional):: 合約
Notes:: Agreement between buyer and seller; generic contract, not only sales contract

protocol

Arabic:: بروتوكول
Czech:: protokol
German:: Protokoll
Greek:: πρωτόκολλο
Spanish:: protocolo
Finnish:: protokolla
French:: protocole
Friulian:: protocol
Galician:: protocolo
Hebrew:: פרוטוקול
Hindi:: प्रोटोकॉल
Hungarian:: protokoll
Italian:: protocollo
Japanese:: プロトコル
Korean:: 프로토콜
Dutch:: protocol
Polish:: protokół
Portuguese:: protocolo
Portuguese (Brazil):: protocolo
Russian:: протокол
Slovak:: protokol
Swedish:: protokoll
Turkish:: protokol
Ukrainian:: протокол
Chinese (Simplified):: 协议
Chinese (Traditional):: 協議

privacy

Arabic:: الخصوصية
Czech:: soukromí
German:: Privatsphäre
Greek:: ιδιωτικότητα
Spanish:: privacidad
Finnish:: yksityisyys
French:: vie privée
Friulian:: riservatece
Galician:: privacidade
Hebrew:: פרטיות
Hindi:: निजता
Hungarian:: magánszféra
Italian:: privacy
Japanese:: プライバシー
Korean:: 사생활
Dutch:: privacy
Polish:: prywatność
Portuguese:: privacidade
Portuguese (Brazil):: privacidade
Russian:: конфиденциальность
Slovak:: súkromie
Swedish:: integritet
Turkish:: mahremiyet
Ukrainian:: конфіденційність
Chinese (Simplified):: 隐私
Chinese (Traditional):: 隱私
Notes:: Personal privacy sphere; not “data protection” or “confidentiality” unless the source distinguishes them

customer

Arabic:: عميل
Czech:: zákazník
German:: Kunde
Greek:: πελάτης
Spanish:: cliente
Finnish:: asiakas
French:: client
Friulian:: client
Galician:: cliente
Hebrew:: לקוח
Hindi:: ग्राहक
Hungarian:: ügyfél
Italian:: cliente
Japanese:: 顧客
Korean:: 고객
Dutch:: klant
Polish:: klient
Portuguese:: cliente
Portuguese (Brazil):: cliente
Russian:: клиент
Slovak:: zákazník
Swedish:: kund
Turkish:: müşteri
Ukrainian:: клієнт
Chinese (Simplified):: 客户
Chinese (Traditional):: 客戶
Notes:: Buyer/consumer using Taler

KYC

Arabic:: اعرف عميلك (KYC)
Czech:: KYC
German:: KYC
Greek:: KYC
Spanish:: KYC
Finnish:: KYC
French:: KYC
Friulian:: KYC
Galician:: KYC
Hebrew:: KYC
Hindi:: KYC
Hungarian:: KYC
Italian:: KYC
Japanese:: 顧客確認（KYC）
Korean:: 고객 확인 제도(KYC)
Dutch:: KYC
Polish:: KYC
Portuguese:: KYC
Portuguese (Brazil):: KYC
Russian:: KYC (Знай своего клиента)
Slovak:: KYC
Swedish:: KYC (Känn din kund)
Turkish:: KYC
Ukrainian:: KYC
Chinese (Simplified):: 了解你的客户 (KYC)
Chinese (Traditional):: 了解您的客戶 (KYC)
Notes:: Keep acronym KYC; gloss in-language on first use if helpful

free software

Arabic:: برمجيات حرة
Czech:: svobodný software
German:: freie Software
Greek:: ελεύθερο λογισμικό
Spanish:: software libre
Finnish:: vapaa ohjelmisto
French:: logiciel libre
Friulian:: software libar
Galician:: software libre
Hebrew:: תוכנה חופשית
Hindi:: मुक्त सॉफ़्टवेयर
Hungarian:: szabad szoftver
Italian:: software libero
Japanese:: 自由ソフトウェア
Korean:: 자유 소프트웨어
Dutch:: vrije software
Polish:: wolne oprogramowanie
Portuguese:: software livre
Portuguese (Brazil):: software livre
Russian:: свободное ПО
Slovak:: slobodný softvér
Swedish:: fri programvara
Turkish:: özgür yazılım
Ukrainian:: вільне ПЗ
Chinese (Simplified):: 自由软件
Chinese (Traditional):: 自由軟體
Notes:: libre / freedom sense – NEVER gratis / free-of-charge

digital cash

Arabic:: النقود الرقمية
Catalan:: efectiu digital
Czech:: digitální hotovost
German:: digitales Bargeld
Greek:: ψηφιακά μετρητά
Spanish:: efectivo digital
Finnish:: digitaalinen käteinen
French:: monnaie numérique
Friulian:: monede digjitâl
Galician:: diñeiro dixital
Hebrew:: מזומן דיגיטלי
Hindi:: डिजिटल नकदी
Hungarian:: digitális készpénz
Italian:: denaro digitale
Japanese:: デジタルキャッシュ
Korean:: 디지털 현금
Dutch:: digitaal contant geld
Polish:: cyfrowa gotówka
Portuguese:: dinheiro digital
Portuguese (Brazil):: dinheiro digital
Russian:: цифровые деньги
Slovak:: digitálna hotovosť
Swedish:: digitala pengar
Turkish:: dijital nakit
Ukrainian:: цифрові гроші
Chinese (Simplified):: 数字现金
Chinese (Traditional):: 數位現金
Notes:: Electronic banknotes (cash sense); not “digital money/currency”

wire transfer

Arabic:: تحويل مصرفي
Czech:: bankovní převod
German:: Banküberweisung
Greek:: τραπεζικό έμβασμα
Spanish:: transferencia bancaria
Finnish:: tilisiirto
French:: virement bancaire
Friulian:: bonific
Galician:: transferencia bancaria
Hebrew:: העברה בנקאית
Hindi:: वायर ट्रांसफर
Hungarian:: banki átutalás
Italian:: bonifico bancario
Japanese:: 送金
Korean:: 전신 송금
Dutch:: overschrijving
Polish:: przelew bankowy
Portuguese:: transferência bancária
Portuguese (Brazil):: transferência bancária
Russian:: банковский перевод
Slovak:: bankový prevod
Swedish:: banköverföring
Turkish:: banka havalesi
Ukrainian:: банківський переказ
Chinese (Simplified):: 电汇
Chinese (Traditional):: 電匯
Notes:: Bank-to-bank transfer (SEPA/SWIFT etc.); also “wire fee”, “wire transfer subject”

anonymous

Arabic:: مجهول
Czech:: anonymní
German:: anonym
Greek:: ανώνυμος
Spanish:: anónimo
Finnish:: anonyymi
French:: anonyme
Friulian:: anonim
Galician:: anónimo
Hebrew:: אנונימי
Hindi:: गुमनाम
Hungarian:: névtelen
Italian:: anonimo
Japanese:: 匿名
Korean:: 익명
Dutch:: anoniem
Polish:: anonimowy
Portuguese:: anónimo
Portuguese (Brazil):: anônimo
Russian:: анонимный
Slovak:: anonymný
Swedish:: anonym
Turkish:: anonim
Ukrainian:: анонімний
Chinese (Simplified):: 匿名
Chinese (Traditional):: 匿名
Notes:: anonymous / anonymity of the payer; privacy-by-design sense

blockchain

Arabic:: سلسلة الكتل
Czech:: blockchain
German:: Blockchain
Greek:: blockchain
Spanish:: blockchain
Finnish:: lohkoketju
French:: blockchain
Friulian:: blockchain
Galician:: blockchain
Hebrew:: בלוקצ’יין
Hindi:: ब्लॉकचेन
Hungarian:: blokklánc
Italian:: blockchain
Japanese:: ブロックチェーン
Korean:: 블록체인
Dutch:: blockchain
Polish:: blockchain
Portuguese:: blockchain
Portuguese (Brazil):: blockchain
Russian:: блокчейн
Slovak:: blockchain
Swedish:: blockkedja
Turkish:: blok zinciri
Ukrainian:: блокчейн
Chinese (Simplified):: 区块链
Chinese (Traditional):: 區塊鏈
Notes:: Distributed ledger; Taler is explicitly NOT a blockchain – keep the standard tech term

tax

Arabic:: ضريبة
Czech:: daň
German:: Steuer
Greek:: φόρος
Spanish:: impuesto
Finnish:: vero
French:: impôt
Friulian:: taie
Galician:: imposto
Hebrew:: מס
Hindi:: कर
Hungarian:: adó
Italian:: imposta
Japanese:: 税
Korean:: 세금
Dutch:: belasting
Polish:: podatek
Portuguese:: imposto
Portuguese (Brazil):: imposto
Russian:: налог
Slovak:: daň
Swedish:: skatt
Turkish:: vergi
Ukrainian:: податок
Chinese (Simplified):: 税务
Chinese (Traditional):: 稅
Notes:: Taxation / taxable; Taler makes income taxable (use the fiscal term, not “fee”)

account

Arabic:: حساب
Catalan:: Compte
Czech:: účet
German:: Konto
Greek:: λογαριασμός
Spanish:: cuenta
Finnish:: tili
French:: compte
Friulian:: cont
Galician:: conta
Hebrew:: חשבון
Hindi:: खाता
Hungarian:: fiók/számla
Italian:: conto
Japanese:: 口座
Korean:: 계좌
Dutch:: rekening
Polish:: konto
Portuguese:: conta
Portuguese (Brazil):: conta
Russian:: счёт
Slovak:: účet
Swedish:: konto
Turkish:: hesap
Ukrainian:: рахунок
Chinese (Simplified):: 账户
Chinese (Traditional):: 帳戶
Notes:: Bank account / user account

transfer

Arabic:: تحويل
Catalan:: Transferència
Czech:: převod
German:: Überweisung
Greek:: μεταφορά
Spanish:: transferencia
Finnish:: siirto
French:: transfert
Friulian:: trasferiment
Galician:: transferencia
Hebrew:: העברה
Hindi:: हस्तांतरण
Hungarian:: átutalás
Italian:: trasferimento
Japanese:: 送金
Korean:: 송금
Dutch:: overdracht
Polish:: przelew
Portuguese:: transferência
Portuguese (Brazil):: transferência
Russian:: перевод
Slovak:: prevod
Swedish:: överföring
Turkish:: transfer
Ukrainian:: переказ
Chinese (Simplified):: 转账
Chinese (Traditional):: 轉帳
Notes:: Move of funds (generic); distinguish from “wire transfer” where source does

security

Arabic:: أمان
Czech:: bezpečnost
German:: Sicherheit
Greek:: ασφάλεια
Spanish:: seguridad
Finnish:: turvallisuus
French:: sécurité
Friulian:: sigurece
Galician:: seguridade
Hebrew:: אבטחה
Hindi:: सुरक्षा
Hungarian:: biztonság
Italian:: sicurezza
Japanese:: セキュリティ
Korean:: 보안
Dutch:: beveiliging
Polish:: bezpieczeństwo
Portuguese:: segurança
Portuguese (Brazil):: segurança
Russian:: безопасность
Slovak:: bezpečnosť
Swedish:: säkerhet
Turkish:: güvenlik
Ukrainian:: безпека
Chinese (Simplified):: 安全
Chinese (Traditional):: 安全
Notes:: Security (of the system/funds)

fraud

Arabic:: احتيال
Czech:: podvod
German:: Betrug
Greek:: απάτη
Spanish:: fraude
Finnish:: petos
French:: fraude
Friulian:: fraut
Galician:: fraude
Hebrew:: הונאה
Hindi:: धोखाधड़ी
Hungarian:: csalás
Italian:: frode
Japanese:: 不正
Korean:: 사기
Dutch:: fraude
Polish:: oszustwo
Portuguese:: fraude
Portuguese (Brazil):: fraude
Russian:: мошенничество
Slovak:: podvod
Swedish:: bedrägeri
Turkish:: dolandırıcılık
Ukrainian:: шахрайство
Chinese (Simplified):: 欺诈
Chinese (Traditional):: 欺詐
Notes:: Fraud / fraudulent activity

regulation

Arabic:: تشريع
Czech:: regulace
German:: Regulierung
Greek:: ρύθμιση
Spanish:: regulación
Finnish:: sääntely
French:: réglementation
Friulian:: regolamentazion
Galician:: regulación
Hebrew:: רגולציה
Hindi:: विनियमन
Hungarian:: szabályozás
Italian:: regolamentazione
Japanese:: 規制
Korean:: 규제
Dutch:: regelgeving
Polish:: regulacja
Portuguese:: regulação
Portuguese (Brazil):: regulamentação
Russian:: регулирование
Slovak:: regulácia
Swedish:: reglering
Turkish:: düzenleme
Ukrainian:: регулювання
Chinese (Simplified):: 监管
Chinese (Traditional):: 法規
Notes:: Financial/legal regulation; “regulatory framework”, GDPR context

audit

Arabic:: تدقيق
Czech:: audit
German:: Audit
Greek:: έλεγχος
Spanish:: auditoría
Finnish:: tarkastus
French:: audit
Friulian:: verifiche
Galician:: auditoría
Hebrew:: ביקורת
Hindi:: लेखा परीक्षा
Hungarian:: ellenőrzés
Italian:: audit
Japanese:: 監査
Korean:: 감사
Dutch:: audit
Polish:: audyt
Portuguese:: auditoria
Portuguese (Brazil):: auditoria
Russian:: аудит
Slovak:: audit
Swedish:: revision
Turkish:: denetim
Ukrainian:: аудит
Chinese (Simplified):: 审计
Chinese (Traditional):: 審計
Notes:: To audit / auditing (the action); auditor is the actor (separate row)

income

Arabic:: دخل
Czech:: příjem
German:: Einkommen
Greek:: εισόδημα
Spanish:: ingresos
Finnish:: tulo
French:: revenu
Friulian:: redit
Galician:: ingresos
Hebrew:: הכנסה
Hindi:: आय
Hungarian:: jövedelem
Italian:: reddito
Japanese:: 所得
Korean:: 소득
Dutch:: inkomen
Polish:: dochód
Portuguese:: rendimento
Portuguese (Brazil):: renda
Russian:: доход
Slovak:: príjem
Swedish:: inkomst
Turkish:: gelir
Ukrainian:: дохід
Chinese (Simplified):: 收入
Chinese (Traditional):: 收入
Notes:: Income/earnings (fiscal sense), e.g. merchant income that is taxable

reserve

Arabic:: احتياطي
Czech:: rezerva
German:: Reserve
Greek:: αποθεματικό
Spanish:: reserva
Finnish:: varanto
French:: réserve
Friulian:: riserve
Galician:: reserva
Hebrew:: עתודה
Hindi:: रिज़र्व
Hungarian:: tartalék
Italian:: riserva
Japanese:: 準備金
Korean:: 준비금
Dutch:: reserve
Polish:: rezerwa
Portuguese:: reserva
Portuguese (Brazil):: reserva
Russian:: резерв
Slovak:: rezerva
Swedish:: reserv
Turkish:: rezerv
Ukrainian:: резерв
Chinese (Simplified):: 储备金
Chinese (Traditional):: 儲備
Notes:: Funds reserved at the exchange after a withdrawal; also TALER acronym “…Electronic Reserves”

refund

Arabic:: استرداد
Catalan:: Reemborsament
Czech:: vrácení peněz
German:: Rückerstattung
Greek:: επιστροφή χρημάτων
Spanish:: reembolso
Finnish:: hyvitys
French:: remboursement
Friulian:: rimbors
Galician:: reembolso
Hebrew:: החזר
Hindi:: धनवापसी
Hungarian:: visszatérítés
Italian:: rimborso
Japanese:: 返金
Korean:: 환불
Dutch:: terugbetaling
Polish:: zwrot
Portuguese:: reembolso
Portuguese (Brazil):: reembolso
Russian:: возврат
Slovak:: vrátenie peňazí
Swedish:: återbetalning
Turkish:: iade
Ukrainian:: повернення коштів
Chinese (Simplified):: 退款
Chinese (Traditional):: 退款
Notes:: Return of a payment to the customer

Amount

Catalan:: Quantitat
German:: Betrag
Spanish:: Monto
Finnish:: Summa
French:: Montant
Hebrew:: סכום
Italian:: Importo
Polish:: kwota
Russian:: Сумма
Slovak:: suma
Turkish:: Miktar
Ukrainian:: Сума
Notes:: it: chose Importo over Somma

Balance

Catalan:: Saldo
German:: Saldo
Spanish:: Saldo
Finnish:: Saldo
French:: Solde
Hebrew:: יתרה
Italian:: Saldo
Japanese:: 残高
Polish:: saldo
Russian:: Баланс
Slovak:: zostatok
Swedish:: Balans
Turkish:: Bakiye
Ukrainian:: Баланс
Notes:: de: chose Saldo over Salden/Guthaben

Account balance

German:: Kontostand
Spanish:: Saldo de la cuenta
French:: Solde du compte
Polish:: stan konta
Slovak:: zostatok na účte
Notes:: de: chose Kontostand over Saldo

Money

German:: Geld
Spanish:: Dinero
French:: Argent
Hebrew:: כסף
Italian:: Denaro
Polish:: pieniądze
Slovak:: peniaze

Cash

German:: Bargeld
Spanish:: Efectivo
French:: Espèces
Hebrew:: מזומן
Italian:: Contante
Polish:: gotówka
Slovak:: hotovosť

Funds

German:: Guthaben
Spanish:: Fondos
French:: Fonds
Hebrew:: כספים
Polish:: środki
Slovak:: finančné prostriedky
Notes:: de: chose Guthaben over Mittel

Price

Catalan:: Preu
German:: Preis
Spanish:: Precio
French:: Prix
Hebrew:: מחיר
Italian:: Prezzo
Polish:: cena
Russian:: Цена
Slovak:: cena
Turkish:: Fiyat
Ukrainian:: Ціна

Total

Catalan:: Total
German:: Gesamt
Spanish:: Total
French:: Total
Hebrew:: סה”כ
Italian:: Totale
Polish:: suma
Russian:: Всего
Slovak:: Celkom
Turkish:: Toplam
Ukrainian:: Загальна сума
Notes:: de: chose Gesamt over Gesamtpreis

Quantity

German:: Menge
Spanish:: Cantidad
French:: Quantité
Hebrew:: כמות
Italian:: Quantità
Polish:: ilość
Slovak:: množstvo
Ukrainian:: Кількість

Stock

German:: Bestand
Spanish:: Stock
French:: Stock
Polish:: zapasy
Slovak:: zásoby
Ukrainian:: Запас

Pay

Catalan:: Pagament
German:: Bezahlen
Spanish:: Pagar
French:: Payer
Hebrew:: שלם
Italian:: Pagare
Polish:: Zapłać
Russian:: Платёж
Slovak:: zaplatiť
Turkish:: Ödeme
Ukrainian:: Оплата
Notes:: verb form; chose Bezahlen/Payer/Pagar over Zahlung/Paiement/Pago (vs Payment noun)

Withdrawal

Catalan:: Retirada
German:: Abhebung
Spanish:: Retirada
Finnish:: Nosto
French:: Retrait
Hebrew:: משיכה
Italian:: Prelievo
Polish:: wypłata
Russian:: Вывод
Slovak:: výber
Turkish:: Çekildi
Ukrainian:: Зняття
Notes:: es: chose Retirada over Extracción (noun; pairs with retirar)

Send

Catalan:: Enviar
German:: Senden
Spanish:: Enviar
Finnish:: Lähetä
French:: Envoyer
Hebrew:: שלח
Italian:: Inviare
Polish:: Wyślij
Slovak:: poslať
Turkish:: Gönder
Notes:: de: Senden over Überweisen; es: Enviar (fixed Envíar typo)

Receive

German:: Erhalten
Spanish:: Recibir
French:: Recevoir
Hebrew:: קבל
Italian:: Ricevere
Polish:: Otrzymaj
Slovak:: prijať

Cashout

German:: Auszahlung
Spanish:: Egreso
French:: Encaissement
Hebrew:: פדיון
Italian:: Cashout
Polish:: wypłata środków
Russian:: Выплата
Slovak:: výplata
Ukrainian:: Виплати готівкою
Notes:: de: Auszahlung (avoid Einzahlung=Deposit); fr: Encaissement (avoid Retrait=Withdrawal)

Refresh

Catalan:: Actualitzar
German:: Erneuern
Spanish:: Renovar
French:: Actualiser
Hebrew:: רענן
Polish:: odświeżenie
Russian:: Обновить
Slovak:: obnoviť
Ukrainian:: Оновити
Notes:: de: Erneuern (avoid Aktualisieren=Update); es: Renovar (avoid Actualizar=Update)

Conversion

German:: Umrechnung
Spanish:: Conversión
French:: Conversion
Italian:: Cambio
Polish:: przewalutowanie
Slovak:: konverzia

Conversion rate

German:: Umrechnungskurs
Spanish:: Tasa de conversión
French:: Taux de conversion
Polish:: kurs wymiany
Russian:: Обменный курс
Slovak:: konverzný kurz
Ukrainian:: Обмінний курс

Transaction fee

German:: Transaktionsgebühr
Spanish:: Comisión de transacción
French:: Frais de transaction
Polish:: opłata za transakcję
Slovak:: transakčný poplatok

Deposit fee

Catalan:: Comissió de dipòsit
German:: Einzahlungsgebühr
Spanish:: Comisión de depósito
French:: Frais de dépôt
Polish:: opłata depozytowa
Russian:: Комиссия депозита
Slovak:: poplatok za vklad
Ukrainian:: Комісія за депозит

Provider

German:: Anbieter
Spanish:: Proveedor
French:: Prestataire
Hebrew:: ספק
Polish:: dostawca
Slovak:: poskytovateľ

Sender

German:: Absender
Spanish:: Remitente
French:: Expéditeur
Hebrew:: שולח
Polish:: nadawca
Slovak:: odosielateľ

Recipient

German:: Empfänger
Spanish:: Destinatario
French:: Destinataire
Hebrew:: נמען
Polish:: odbiorca
Russian:: Получатель
Slovak:: príjemca
Ukrainian:: Одержувач

Beneficiary

German:: Begünstigter
Spanish:: Beneficiario
French:: Bénéficiaire
Polish:: beneficjent
Slovak:: oprávnený príjemca

Bank account

Catalan:: Compte bancari
German:: Bankkonto
Spanish:: Cuenta bancaria
Finnish:: Pankkitili
French:: Compte bancaire
Hebrew:: חשבון בנק
Polish:: konto bankowe
Russian:: Банковский счёт
Slovak:: bankový účet
Swedish:: Bankkonto
Turkish:: Banka hesabı
Ukrainian:: Банківський рахунок

IBAN

Catalan:: IBAN
German:: IBAN
Spanish:: IBAN
Finnish:: IBAN
French:: IBAN
Italian:: IBAN
Polish:: IBAN
Russian:: IBAN
Slovak:: IBAN
Turkish:: IBAN
Ukrainian:: IBAN

Debit

Catalan:: Dèbit
German:: Soll
Spanish:: Débito
French:: Débit
Hebrew:: חיוב
Polish:: obciążenie
Russian:: Дебит
Slovak:: debet
Ukrainian:: Дебет
Notes:: de: chose Soll over Lastschrift

Credit

Catalan:: Crèdit
German:: Guthaben
Spanish:: Crédito
French:: Crédit
Hebrew:: זיכוי
Polish:: uznanie
Russian:: Кредит
Slovak:: kredit
Turkish:: Kredi
Ukrainian:: Кредит

Subject

Catalan:: Concepte
German:: Buchungsvermerk
Spanish:: Asunto
Finnish:: Aihe
French:: Référence
Hebrew:: פרטי העברה
Italian:: Soggetto
Polish:: tytuł przelewu
Russian:: Причина
Slovak:: predmet
Turkish:: Konu
Ukrainian:: Призначення

Order

German:: Bestellung
Spanish:: Pedido
French:: Commande
Hebrew:: הזמנה
Polish:: zamówienie
Slovak:: objednávka
Ukrainian:: Замовлення
Notes:: es: chose Pedido over Orden

Invoice

Catalan:: Factura
Czech:: Faktura
German:: Rechnung
Greek:: Τιμολόγιο
Spanish:: Factura
French:: Facture
Hebrew:: חשבונית
Hungarian:: Számla
Italian:: Fattura
Japanese:: 請求書
Dutch:: Factuur
Polish:: faktura
Portuguese:: Fatura
Russian:: Счёт-фактура
Slovak:: faktúra
Turkish:: Fatura
Ukrainian:: Рахунок-фактура
Notes:: Billing/accounting document (Dolibarr).

Token

German:: Zugangstoken
Spanish:: Token
French:: Jeton
Polish:: token
Slovak:: token

Terms of service

Catalan:: termes del servei
German:: Allgemeine Geschäftsbedingungen (AGB)
Spanish:: Términos de servicio
French:: Conditions d’utilisation
Hebrew:: תנאי השירות
Polish:: warunki korzystania z usługi
Slovak:: podmienky používania
Notes:: fr: chose Conditions d’utilisation over Conditions Générales d’Utilisation

Pending

German:: Ausstehend
Spanish:: Pendiente
French:: En attente
Hebrew:: ממתין
Polish:: oczekujące
Slovak:: čakajúce

Completed

German:: Abgeschlossen
Spanish:: Completado
French:: Terminé
Hebrew:: הושלם
Polish:: zakończone
Slovak:: dokončené

Confirmed

German:: Bestätigt
Spanish:: Confirmado
French:: Confirmé
Hebrew:: אושר
Polish:: potwierdzone
Slovak:: potvrdené
Ukrainian:: Підтверджено

Paid

German:: Bezahlt
Spanish:: Pagado
French:: Payée
Hebrew:: שולם
Polish:: opłacone
Slovak:: zaplatené
Ukrainian:: Оплачено

Unpaid

German:: Noch nicht bezahlt
Spanish:: Impago
French:: Non payé
Hebrew:: לא שולם
Polish:: nieopłacone
Slovak:: nezaplatené
Ukrainian:: Неоплачено

Failed

German:: Fehlgeschlagen
Spanish:: Fallido
French:: Échoué
Hebrew:: נכשל
Polish:: nieudane
Slovak:: zlyhalo

Aborted

German:: Abgebrochen
Spanish:: Cancelado
French:: Abandonné
Hebrew:: בוטל
Polish:: przerwane
Slovak:: prerušené

Refunded

Catalan:: Reemborsat
German:: Rückerstattet
Spanish:: Reembolsado
French:: Remboursée
Hebrew:: הוחזר
Italian:: Rimborsato
Polish:: zwrócone
Russian:: Возвращено на счёт
Slovak:: refundované
Turkish:: İade edildi
Ukrainian:: Повернено

Expired

German:: Abgelaufen
Spanish:: Vencido
French:: Expiré
Hebrew:: פג תוקף
Polish:: wygasłe
Slovak:: vypršané

Confirm

Catalan:: Confirmar
German:: Bestätigen
Spanish:: Confirmar
Finnish:: Vahvista
French:: Confirmer
Hebrew:: אשר
Italian:: Confermare
Polish:: Potwierdź
Russian:: Подтвердить
Slovak:: potvrdiť
Swedish:: Bekräfta
Turkish:: Onaylamak
Ukrainian:: Підтвердити

Cancel

Catalan:: Cancel·lar
German:: Abbrechen
Spanish:: Cancelar
Finnish:: Peruuta
French:: Annuler
Hebrew:: בטל
Italian:: Annullare
Polish:: Anuluj
Russian:: Отмена
Slovak:: zrušiť
Swedish:: Avbryt
Turkish:: İptal
Ukrainian:: Скасувати

Continue

German:: Weiter
Spanish:: Continuar
French:: Continuer
Hebrew:: המשך
Polish:: Kontynuuj
Russian:: Продолжить
Slovak:: pokračovať
Ukrainian:: Продовжити

Back

German:: Zurück
Spanish:: Volver
French:: Retour
Hebrew:: חזור
Italian:: Indietro
Polish:: Wstecz
Slovak:: späť
Ukrainian:: Назад

Next

Catalan:: Següent
German:: Weiter
Spanish:: Siguiente
French:: Suivant
Hebrew:: הבא
Polish:: Dalej
Russian:: Далее
Slovak:: ďalej
Ukrainian:: Далі
Notes:: de: chose Weiter over Nächste (same as Continue)

Close

Catalan:: Tancar
German:: Schließen
Spanish:: Cerrar
French:: Fermer
Hebrew:: סגור
Polish:: Zamknij
Russian:: Закрыть
Slovak:: zavrieť
Ukrainian:: Закрити

Add

Catalan:: Afegir
German:: Hinzufügen
Spanish:: Añadir
Finnish:: Lisää
French:: Ajouter
Hebrew:: הוסף
Polish:: Dodaj
Russian:: Добавить
Slovak:: pridať
Turkish:: Ekle
Ukrainian:: Додати
Notes:: es: chose Añadir over Agregar

Create

Catalan:: Crear
German:: Erstellen
Spanish:: Crear
French:: Créer
Hebrew:: צור
Polish:: Utwórz
Russian:: Создать
Slovak:: vytvoriť
Ukrainian:: Створити
Notes:: de: chose Erstellen over Anlegen

Edit

Catalan:: Editar
German:: Bearbeiten
Spanish:: Editar
French:: Modifier
Hebrew:: ערוך
Polish:: Edytuj
Russian:: Изменить
Slovak:: upraviť
Ukrainian:: Редагувати
Notes:: fr: chose Modifier over Éditer

Update

German:: Aktualisieren
Spanish:: Actualizar
French:: Modifier
Polish:: Aktualizuj
Russian:: Обновить
Slovak:: aktualizovať
Ukrainian:: Оновити
Notes:: fr: Modifier (shared with Edit)

Delete

German:: Löschen
Spanish:: Eliminar
French:: Supprimer
Hebrew:: מחק
Polish:: Usuń
Russian:: Удалить
Slovak:: odstrániť
Ukrainian:: Видалити
Notes:: es: chose Eliminar over Borrar

Remove

German:: Entfernen
Spanish:: Quitar
French:: Supprimer
Hebrew:: הסר
Polish:: Usuń
Russian:: Удалить
Slovak:: odstrániť
Ukrainian:: Видалити
Notes:: fr: Supprimer (avoid Retirer=Withdraw); es: Quitar (avoid Eliminar=Delete)

Accept

Catalan:: Acceptar
German:: Akzeptieren
Spanish:: Aceptar
French:: Accepter
Hebrew:: קבל
Polish:: Akceptuj
Russian:: Принять
Slovak:: prijať
Ukrainian:: Прийняти

Verify

German:: Überprüfen
Spanish:: Verificar
French:: Vérifier
Hebrew:: אמת
Polish:: Zweryfikuj
Slovak:: overiť
Notes:: de: chose Überprüfen over Prüfen (pairs with Überprüfung)

Verification

German:: Überprüfung
Spanish:: Verificación
French:: Vérification
Polish:: weryfikacja
Russian:: Проверка
Slovak:: overenie
Ukrainian:: Підтвердження

Log in

German:: Anmelden
Spanish:: Ingresar
French:: Se connecter
Hebrew:: התחבר
Polish:: Zaloguj się
Russian:: Войти
Slovak:: prihlásiť sa
Ukrainian:: Увійти

Log out

German:: Abmelden
Spanish:: Cerrar sesión
French:: Déconnexion
Hebrew:: התנתק
Polish:: Wyloguj się
Slovak:: odhlásiť sa
Ukrainian:: Вийти

Password

German:: Passwort
Spanish:: Contraseña
French:: Mot de passe
Polish:: Hasło
Russian:: Пароль
Slovak:: heslo
Ukrainian:: Пароль

Username

German:: Benutzername
Spanish:: Usuario
French:: Nom d’utilisateur
Polish:: Nazwa użytkownika
Russian:: Имя пользователя
Slovak:: používateľské meno
Ukrainian:: Імʼя користувача
Notes:: de: Benutzername over Nutzername; fr: Nom d’utilisateur over Identifiant

Name

Catalan:: Nom
German:: Name
Spanish:: Nombre
French:: Nom
Polish:: nazwa
Russian:: Название
Slovak:: názov
Ukrainian:: Назва

Email

German:: E-Mail
Spanish:: Correo electrónico
French:: Courriel
Polish:: E-mail
Russian:: Email
Slovak:: e-mail
Ukrainian:: Email
Notes:: fr: chose Courriel over Adresse mail

Address

Catalan:: Adreça
German:: Adresse
Spanish:: Dirección
French:: Adresse
Polish:: adres
Slovak:: adresa
Turkish:: Adres
Ukrainian:: Адреса

Phone

German:: Telefon
Spanish:: Teléfono
French:: Téléphone
Polish:: Telefon
Russian:: Телефон
Slovak:: telefón
Ukrainian:: Телефон

Date

Catalan:: Data
German:: Datum
Spanish:: Fecha
French:: Date
Italian:: Data
Polish:: Data
Russian:: Дата
Slovak:: dátum
Turkish:: Tarih
Ukrainian:: Дата

Approve refund

Hebrew:: אשר החזר
Polish:: Zatwierdź zwrot
Slovak:: schváliť vrátenie peňazí
Notes:: merchants “approve” refunds (project terminology)

Settings

Catalan:: Configuració
German:: Einstellungen
Spanish:: Configuración
Finnish:: Asetukset
French:: Paramètres
Hebrew:: הגדרות
Italian:: Impostazioni
Japanese:: 設定
Dutch:: Instellingen
Polish:: Ustawienia
Russian:: Настройки
Slovak:: nastavenia
Swedish:: Inställningar
Turkish:: Ayarlar
Ukrainian:: Налаштування
Notes:: fr: chose Paramètres over Configuration/Options; unify UI ‘Settings’

Status

Catalan:: Estat
German:: Status
Spanish:: Estado
French:: Statut
Hebrew:: סטטוס
Italian:: Stato
Dutch:: Status
Polish:: status
Russian:: Статус
Slovak:: stav
Swedish:: Status
Turkish:: Durum
Ukrainian:: Статус
Notes:: fr: chose Statut over État/Situation

Log in

German:: Anmelden
Spanish:: Iniciar sesión
French:: Se connecter
Hebrew:: התחבר
Italian:: Accedi
Polish:: Zaloguj się
Russian:: Войти
Slovak:: prihlásiť sa
Turkish:: Giriş yap
Ukrainian:: Увійти
Notes:: pair with Log out; several catalogs had Log in/out swapped

Log out

German:: Abmelden
Spanish:: Cerrar sesión
French:: Déconnexion
Hebrew:: התנתק
Italian:: Esci
Polish:: Wyloguj się
Russian:: Выйти
Slovak:: odhlásiť sa
Turkish:: Çıkış yap
Ukrainian:: Вийти
Notes:: es/fr/de/uk catalogs had this rendered as ‘Log in’ (opposite) — pin it

Counterparty

German:: Gegenpartei
Spanish:: Contraparte
French:: Contrepartie
Hebrew:: צד שכנגד
Italian:: Controparte
Polish:: druga strona
Slovak:: protistrana
Notes:: it was mistranslated ‘Conto corrente’ (current account); the other party in a transaction

Instance

German:: Instanz
Spanish:: instancia
French:: instance
Hebrew:: מופע
Italian:: istanza
Polish:: instancja
Slovak:: inštancia
Swedish:: Instans
Ukrainian:: екземпляр
Notes:: merchant multi-tenant term; es feminine (una instancia) — watch agreement

Fulfillment message

Spanish:: Mensaje de cumplimiento
Polish:: komunikat realizacji
Slovak:: správa o plnení
Ukrainian:: Повідомлення про виконання
Notes:: keep distinct from ‘Fulfillment URL’; conflated in several catalogs

Reset

Catalan:: Restablir
German:: Zurücksetzen
Spanish:: Restablecer
French:: Réinitialiser
Hebrew:: איפוס
Italian:: Reimposta
Polish:: Zresetuj
Slovak:: resetovať
Notes:: ca: chose Restablir over anglicism ‘resetejar’

Loading

Catalan:: Carregant
German:: Wird geladen
Spanish:: Cargando
Finnish:: Ladataan
French:: Chargement
Hebrew:: טוען
Italian:: Caricamento
Polish:: Ładowanie
Slovak:: načítava sa
Notes:: status text, not imperative; fi had imperative ‘Lataa’

Search

German:: Suchen
Spanish:: Buscar
French:: Rechercher
Hebrew:: חיפוש
Italian:: Cerca
Polish:: Wyszukaj
Slovak:: vyhľadať

Denomination

German:: Denomination
Spanish:: denominación
Finnish:: nimellisarvo
French:: dénomination
Hebrew:: ערך נקוב
Italian:: taglio
Dutch:: denominatie
Polish:: nominał
Russian:: деноминация
Slovak:: denominácia
Swedish:: valör
Turkish:: değer birimi
Ukrainian:: номінал
Notes:: Taler technical term: a coin’s value class / signing-key denomination; some locales keep English ‘Denomination’

Webhook

German:: Webhook
Spanish:: webhook
French:: webhook
Hebrew:: webhook
Italian:: webhook
Dutch:: webhook
Polish:: webhook
Russian:: вебхук
Slovak:: webhook
Swedish:: webhook
Turkish:: webhook
Ukrainian:: вебхук
Notes:: keep as loanword; inflect natively where needed

Purge

German:: Endgültig löschen
Spanish:: purgar
French:: purger
Hebrew:: מחיקה סופית
Italian:: Elimina definitivamente
Polish:: Trwałe usunięcie
Slovak:: vyčistiť
Turkish:: Kalıcı Sil
Ukrainian:: остаточно видалити
Notes:: hard delete that also destroys associated data; keep DISTINCT from Delete

Money pot

German:: Sammeltopf
Spanish:: bote
French:: cagnotte
Italian:: salvadanaio
Polish:: skarbonka
Slovak:: pokladnička
Swedish:: pott
Turkish:: fon
Ukrainian:: скарбничка
Notes:: merchant collection/fundraising pot feature; whimsical source term

Access token

German:: Zugangstoken
Spanish:: token de acceso
French:: jeton d’accès
Hebrew:: אסימון גישה
Italian:: token di accesso
Polish:: token dostępu
Russian:: токен доступа
Slovak:: prístupový token
Turkish:: erişim belirteci
Ukrainian:: токен доступу
Notes:: API/session access token

Cashin

German:: Einzahlung
Spanish:: ingreso
French:: versement
Hebrew:: הפקדה
Italian:: Cashin
Polish:: wpłata
Russian:: пополнение
Slovak:: vloženie hotovosti
Ukrainian:: внесення готівки
Notes:: counterpart of Cashout (fiat -> Taler balance in the bank demo)

Beneficial owner

German:: wirtschaftlich Berechtigte(r)
Spanish:: beneficiario efectivo
French:: ayant droit économique
Hebrew:: בעל שליטה
Italian:: titolare effettivo
Polish:: beneficjent rzeczywisty
Slovak:: konečný užívateľ výhod
Notes:: AML/KYC (VQF form) standard legal term

Controlling person

German:: Kontrollinhaber
Spanish:: persona con poder de control
French:: personne de contrôle
Italian:: persona che esercita il controllo
Polish:: osoba kontrolująca
Slovak:: kontrolujúca osoba
Notes:: Swiss VQF form 902.11 term is ‘Kontrollinhaber’ (used in the KYC forms); ‘kontrollierende Person’ is the general German/EU-GwG synonym. es/fr in the VQF forms: ‘persona que ejerce el control’ / ‘personne de contrôle’.

product

Arabic:: منتج
Catalan:: producte
Czech:: produkt
German:: Produkt
Greek:: προϊόν
Spanish:: producto
Finnish:: tuote
French:: produit
Galician:: produto
Hebrew:: מוצר
Hindi:: उत्पाद
Hungarian:: termék
Italian:: prodotto
Japanese:: 商品
Korean:: 상품
Dutch:: product
Polish:: produkt
Portuguese:: produto
Portuguese (Brazil):: produto
Russian:: товар
Slovak:: produkt
Swedish:: produkt
Turkish:: ürün
Ukrainian:: товар
Chinese (Simplified):: 商品
Chinese (Traditional):: 商品
Notes:: Shop item offered for sale (retail sense). SK produkt (not výrobok/tovar); JA 商品 (not 製品). Added 2026-07.

template

Arabic:: قالب
Catalan:: plantilla
Czech:: šablona
German:: Vorlage
Greek:: πρότυπο
Spanish:: plantilla
Finnish:: malli
French:: modèle
Galician:: modelo
Hebrew:: תבנית
Hindi:: टेम्पलेट
Hungarian:: sablon
Italian:: modello
Japanese:: テンプレート
Korean:: 템플릿
Dutch:: sjabloon
Polish:: szablon
Portuguese:: modelo
Portuguese (Brazil):: modelo
Russian:: шаблон
Slovak:: šablóna
Swedish:: mall
Turkish:: şablon
Ukrainian:: шаблон
Chinese (Simplified):: 模板
Chinese (Traditional):: 範本
Notes:: Order/page template in the merchant backend; do not leave as English. Added 2026-07.

inventory

Arabic:: المخزون
Catalan:: inventari
Czech:: sklad
German:: Bestand
Greek:: απόθεμα
Spanish:: inventario
Finnish:: varasto
French:: inventaire
Galician:: inventario
Hebrew:: מלאי
Hindi:: इन्वेंटरी
Hungarian:: készlet
Italian:: inventario
Japanese:: 在庫
Korean:: 재고
Dutch:: voorraad
Polish:: zapasy
Portuguese:: inventário
Portuguese (Brazil):: inventário
Russian:: запасы
Slovak:: zásoby
Swedish:: lager
Turkish:: envanter
Ukrainian:: запаси
Chinese (Simplified):: 库存
Chinese (Traditional):: 庫存
Notes:: Merchant product-stock catalog/feature (stock-levels sense). SK zásoby, PL zapasy (not sklad/magazyn/inventár). Related to but distinct from single-item “Stock”. Added 2026-07.

category

Arabic:: فئة
Catalan:: categoria
Czech:: kategorie
German:: Kategorie
Greek:: κατηγορία
Spanish:: categoría
Finnish:: luokka
French:: catégorie
Galician:: categoría
Hebrew:: קטגוריה
Hindi:: श्रेणी
Hungarian:: kategória
Italian:: categoria
Japanese:: カテゴリ
Korean:: 카테고리
Dutch:: categorie
Polish:: kategoria
Portuguese:: categoria
Portuguese (Brazil):: categoria
Russian:: категория
Slovak:: kategória
Swedish:: kategori
Turkish:: kategori
Ukrainian:: категорія
Chinese (Simplified):: 类别
Chinese (Traditional):: 類別
Notes:: Product category within the inventory. Added 2026-07.

POS

Arabic:: POS
Catalan:: POS
Czech:: POS
German:: POS
Greek:: POS
Spanish:: POS
Finnish:: POS
French:: POS
Friulian:: POS
Galician:: POS
Hebrew:: POS
Hindi:: POS
Hungarian:: POS
Italian:: POS
Japanese:: POS
Korean:: POS
Dutch:: POS
Polish:: POS
Portuguese:: POS
Portuguese (Brazil):: POS
Russian:: POS
Slovak:: POS
Swedish:: POS
Turkish:: POS
Ukrainian:: POS
Chinese (Simplified):: POS
Chinese (Traditional):: POS
Notes:: Acronym for the point-of-sale app (NOT the separate cashier app — do not conflate the two). Keeping the acronym is fine, but on each page introduce the translated expanded form (see “Point of Sale”) at the FIRST use in MAIN TEXT (not titles), e.g. English “Point of Sale (PoS)”, then use the acronym. Gloss like KYC.

Point of Sale

Arabic:: نقطة البيع
Catalan:: punt de venda
Czech:: prodejní místo
German:: Verkaufsstelle
Greek:: σημείο πώλησης
Spanish:: punto de venta
Finnish:: myyntipiste
French:: point de vente
Galician:: punto de venda
Hebrew:: נקודת מכירה
Hindi:: बिक्री केंद्र
Hungarian:: értékesítési pont
Italian:: punto vendita
Japanese:: 販売時点
Korean:: 판매 시점
Dutch:: verkooppunt
Polish:: punkt sprzedaży
Portuguese:: ponto de venda
Portuguese (Brazil):: ponto de venda
Russian:: точка продаж
Slovak:: predajné miesto
Swedish:: försäljningsställe
Turkish:: satış noktası
Ukrainian:: точка продажу
Chinese (Simplified):: 销售点
Chinese (Traditional):: 銷售點
Notes:: Expanded form of the POS acronym (the point-of-sale app; NOT the checkout/cash-register or cashier sense). Use this translated expansion at the first main-text use on a page, e.g. “Point of Sale (PoS)”, then switch to the acronym. Added 2026-07.

backend

Arabic:: backend
Catalan:: backend
Czech:: backend
German:: Backend
Greek:: backend
Spanish:: backend
Finnish:: backend
French:: backend
Galician:: backend
Hebrew:: backend
Hindi:: backend
Hungarian:: backend
Italian:: backend
Japanese:: バックエンド
Korean:: backend
Dutch:: backend
Polish:: backend
Portuguese:: backend
Portuguese (Brazil):: backend
Russian:: backend
Slovak:: backend
Swedish:: backend
Turkish:: backend
Ukrainian:: backend
Chinese (Simplified):: 后端
Chinese (Traditional):: 後端
Notes:: Merchant backend (server component). Keep English loanword; inflect natively (e.g. de “des Backends”). JA established バックエンド. Hebrew currently varies (קצה אחורי / English) — pin to English. Added 2026-07.

frontend

Arabic:: frontend
Catalan:: frontend
Czech:: frontend
German:: Frontend
Greek:: frontend
Spanish:: frontend
Finnish:: frontend
French:: frontend
Galician:: frontend
Hebrew:: frontend
Hindi:: frontend
Hungarian:: frontend
Italian:: frontend
Japanese:: フロントエンド
Korean:: frontend
Dutch:: frontend
Polish:: frontend
Portuguese:: frontend
Portuguese (Brazil):: frontend
Russian:: frontend
Slovak:: frontend
Swedish:: frontend
Turkish:: frontend
Ukrainian:: frontend
Chinese (Simplified):: 前端
Chinese (Traditional):: 前端
Notes:: Merchant frontend (shop-facing component). Keep English loanword. JA established フロントエンド. Added 2026-07.

QR code

Arabic:: رمز QR
Catalan:: codi QR
Czech:: QR kód
German:: QR-Code
Greek:: κωδικός QR
Spanish:: código QR
Finnish:: QR-koodi
French:: code QR
Galician:: código QR
Hebrew:: קוד QR
Hindi:: क्यूआर कोड
Hungarian:: QR-kód
Italian:: codice QR
Japanese:: QRコード
Korean:: QR 코드
Dutch:: QR-code
Polish:: kod QR
Portuguese:: código QR
Portuguese (Brazil):: código QR
Russian:: QR-код
Slovak:: QR kód
Swedish:: QR-kod
Turkish:: QR kodu
Ukrainian:: QR-код
Chinese (Simplified):: 二维码
Chinese (Traditional):: QR碼
Notes:: QR code shown for the wallet to scan. Added 2026-07.

session

Arabic:: جلسة
Catalan:: sessió
Czech:: relace
German:: Sitzung
Greek:: συνεδρία
Spanish:: sesión
Finnish:: istunto
French:: session
Galician:: sesión
Hebrew:: הפעלה
Hindi:: सत्र
Hungarian:: munkamenet
Italian:: sessione
Japanese:: セッション
Korean:: 세션
Dutch:: sessie
Polish:: sesja
Portuguese:: sessão
Portuguese (Brazil):: sessão
Russian:: сессия
Slovak:: relácia
Swedish:: session
Turkish:: oturum
Ukrainian:: сесія
Chinese (Simplified):: 会话
Chinese (Traditional):: 工作階段
Notes:: Session-bound payment / login session. Added 2026-07.

sandbox

Arabic:: sandbox
Catalan:: sandbox
Czech:: sandbox
German:: sandbox
Greek:: sandbox
Spanish:: sandbox
Finnish:: sandbox
French:: sandbox
Friulian:: sandbox
Galician:: sandbox
Hebrew:: sandbox
Hindi:: sandbox
Hungarian:: sandbox
Italian:: sandbox
Japanese:: sandbox
Korean:: sandbox
Dutch:: sandbox
Polish:: sandbox
Portuguese:: sandbox
Portuguese (Brazil):: sandbox
Russian:: sandbox
Slovak:: sandbox
Swedish:: sandbox
Turkish:: sandbox
Ukrainian:: sandbox
Chinese (Simplified):: sandbox
Chinese (Traditional):: sandbox
Notes:: In these tutorials “sandbox” is a LITERAL identifier — the demo bank/instance name and access credential (e.g. Username: sandbox, …/instances/sandbox/). Never translate it. (As a general concept some languages do translate “sandbox”, but here it is a proper-noun value.)

endpoint

Arabic:: نقطة نهاية
Catalan:: punt de connexió
Czech:: koncový bod
German:: Endpunkt
Greek:: τελικό σημείο
Spanish:: punto de conexión
Finnish:: päätepiste
French:: point de terminaison
Galician:: punto de conexión
Hebrew:: נקודת קצה
Hindi:: एंडपॉइंट
Hungarian:: végpont
Italian:: endpoint
Japanese:: エンドポイント
Korean:: 엔드포인트
Dutch:: endpoint
Polish:: punkt końcowy
Portuguese:: ponto de extremidade
Portuguese (Brazil):: ponto de extremidade
Russian:: конечная точка
Slovak:: koncový bod
Swedish:: slutpunkt
Turkish:: uç noktası
Ukrainian:: кінцева точка
Chinese (Simplified):: 端点
Chinese (Traditional):: 端點
Notes:: HTTP API endpoint. Follow each target language’s technical-documentation convention: many languages translate (de Endpunkt, fr point de terminaison, ru конечная точка, pl punkt końcowy, he נקודת קצה), others keep the English loanword (it, nl, sv-dev). Not a blanket keep-English rule — pick what is clearly understood in that language.

Wire method

Czech:: způsob převodu
German:: Überweisungsmethode
Spanish:: método de transferencia
French:: méthode de virement
Hebrew:: שיטת העברה בנקאית
Hungarian:: átutalási mód
Italian:: metodo di bonifico
Dutch:: overschrijvingsmethode
Polish:: metoda przelewu
Portuguese:: método de transferência
Russian:: способ перевода
Slovak:: spôsob prevodu
Ukrainian:: спосіб переказу
Notes:: Bank-transfer (payto) method UI field. NOT the physical “wire/cable” sense — HE/SK/others mistranslate as cable (שיטת חוט / prenos kábla). Added 2026-07.

Credit note

Czech:: Dobropis
German:: Gutschrift
Greek:: Πιστωτικό σημείωμα
Spanish:: Nota de crédito
French:: Avoir
Hebrew:: זיכוי
Hungarian:: Jóváíró számla
Italian:: Nota di credito
Japanese:: クレジットノート
Dutch:: Creditnota
Polish:: Nota kredytowa
Portuguese:: Nota de crédito
Russian:: Кредит-нота
Slovak:: Dobropis
Ukrainian:: Кредит-нота
Notes:: Accounting document for a refund/return (Dolibarr/TalerBarr); distinct from a Taler ‘refund’ object. Retail/accounting sense.

Supplier

Czech:: Dodavatel
German:: Lieferant
Greek:: Προμηθευτής
Spanish:: Proveedor
French:: Fournisseur
Hebrew:: ספק
Hungarian:: Beszállító
Italian:: Fornitore
Japanese:: 仕入先
Dutch:: Leverancier
Polish:: Dostawca
Portuguese:: Fornecedor
Russian:: Поставщик
Slovak:: Dodávateľ
Ukrainian:: Постачальник
Notes:: Also renders ‘Vendor’ (Dolibarr Vendors module). Retail/procurement sense; the seller/business is ‘merchant’, not this.

20.1.11. iOS Apps#

20.1.11.1. Building Taler Wallet for iOS from source#

The GNU Taler Wallet iOS app is in the official Git repository.

20.1.11.1.1. Compatibility#

The minimum version of iOS supported is 15.0. This app runs on all iPhone models at least as new as the iPhone 6S.

20.1.11.1.2. Building#

Before building the iOS wallet, you must first checkout the quickjs-tart repo and the wallet-core repo.

Have all 3 local repos (wallet-core, quickjs-tart, and this one) adjacent at the same level (e.g. in a “GNU_Taler” folder) Taler.xcworkspace expects the QuickJS framework sub-project to be at ../quickjs-tart/QuickJS-rt.xcodeproj.

Build wallet-core first:

$ cd wallet-core
$ make embedded
$ open packages/taler-wallet-embedded/dist

then drag or move its product “taler-wallet-core-qjs.mjs” into your quickjs-tart folder right at the top level.

Open Taler.xcworkspace, and set scheme / target to Taler_Wallet. Build&run…

Don’t open QuickJS-rt.xcodeproj or TalerWallet.xcodeproj and build anything there - all needed libraries and frameworks will be built automatically from Taler.xcworkspace.

20.1.12. Android Apps#

20.1.12.1. Android App Nightly Builds#

There are currently three Android apps in the official Git repository:

Wallet [CI]
Merchant PoS Terminal [CI]
Cashier [CI]

Their git repositories are mirrored at Gitlab to utilize their CI and F-Droid’s Gitlab integration to publish automatic nightly builds for each change on the master branch.

All three apps publish their builds to the same F-Droid nightly repository (which is stored as a git repository): gnu-taler/fdroid-repo-nightly

You can download the APK files directly from that repository or add it to the F-Droid app for automatic updates by clicking the following link (on the phone that has F-Droid installed).

GNU Taler Nightly F-Droid Repository

Note

Nightly apps can be installed alongside official releases and thus are meant only for testing purposes. Use at your own risk!

20.1.12.2. Building apps from source#

Note that this guide is different from other guides for building Android apps, because it does not require you to run non-free software. It uses the Merchant PoS Terminal as an example, but works as well for the other apps if you replace merchant-terminal with wallet or cashier.

First, ensure that you have the required dependencies installed:

Java Development Kit 8 or higher (default-jdk-headless)
git
unzip

Then you can get the app’s source code using git:

# Start by cloning the Android git repository
$ git clone https://git.taler.net/taler-android.git

# Change into the directory of the cloned repository
$ cd taler-android

# Find out which Android SDK version you will need
$ grep -i compileSdkVersion merchant-terminal/build.gradle

The last command will return something like compileSdkVersion 29. So visit the Android Rebuilds project and look for that version of the Android SDK there. If the SDK version is not yet available as a free rebuild, you can try to lower the compileSdkVersion in the app’s merchant-terminal/build.gradle file. Note that this might break things or require you to also lower other versions such as targetSdkVersion.

In our example, the version is 29 which is available, so download the “SDK Platform” package of “Android 10.0.0 (API 29)” and unpack it:

# Change into the directory that contains your downloaded SDK
$ cd $HOME

# Unpack/extract the Android SDK
$ unzip android-sdk_eng.10.0.0_r14_linux-x86.zip

# Tell the build system where to find the SDK
$ export ANDROID_SDK_ROOT="$HOME/android-sdk_eng.10.0.0_r14_linux-x86"

# Change into the directory of the cloned repository
$ cd taler-android

# Build the merchant-terminal app
$ ./gradlew :merchant-terminal:assembleRelease

If you get an error message complaining about build-tools

> Failed to install the following Android SDK packages as some licences have not been accepted.
build-tools;29.0.3 Android SDK Build-Tools 29.0.3

you can try changing the buildToolsVersion in the app’s merchant-terminal/build.gradle file to the latest “Android SDK build tools” version supported by the Android Rebuilds project.

After the build finished successfully, you will find your APK in merchant-terminal/build/outputs/apk/release/.

20.1.12.3. Update translations#

Translations are managed with Taler’s weblate instance: https://weblate.taler.net/projects/gnu-taler/

To update translations, enter the taler-android git repository and ensure that the weblate remote exists:

$ git config -l | grep weblate

If it does not yet exist (empty output), you can add it like this:

$ git remote add weblate https://weblate.taler.net/git/gnu-taler/wallet-android/

Then you can merge in translations commit from the weblate remote:

# ensure you have latest version
$ git fetch weblate

# merge in translation commits
$ git merge weblate/master

Afterwards, build the entire project from source and test the UI to ensure that no erroneous translations (missing placeholders) are breaking things.

20.1.12.4. Release process#

After extensive testing, the code making up a new release should get a signed git tag. The current tag format is:

cashier-$VERSION
pos-$VERSION
wallet-$VERSION (where $VERSION has a v prefix)

$ git tag -s $APP-$VERSION

20.1.12.4.1. F-Droid#

Nightly builds get published automatically (see above) after pushing code to the official repo. Actual releases get picked up by F-Droid’s official repository via git tags. So ensure that all releases get tagged properly.

Some information for F-Droid official repository debugging:

Wallet: [metadata] [build log]
Cashier: [metadata] [build log]
PoS: [metadata] [build log]

20.1.12.4.2. Google Play#

Google Play uploads are managed via Fastlane. Before proceeding, ensure that this is properly set up and that you have access to the Google Play API.

It is important to have access to the signing keys and Google Play access keys (JSON) and to ensure that the following environment variables are set correctly and made available to Fastlane:

TALER_KEYSTORE_PATH=
TALER_KEYSTORE_PASS=
TALER_KEYSTORE_WALLET_ALIAS=
TALER_KEYSTORE_WALLET_PASS=
TALER_KEYSTORE_POS_ALIAS=
TALER_KEYSTORE_POS_PASS=
TALER_KEYSTORE_CASHIER_ALIAS=
TALER_KEYSTORE_CASHIER_PASS=
TALER_JSON_KEY_FILE=

To release an app, enter into its respective folder and run fastlane:

$ bundle exec fastlane

Then select the deploy option.

All uploads are going to the beta track by default. These can be promoted to production later or immediately after upload if you feel daring. It is also important to bump the version and build code with every release.

20.1.13. Code Coverage#

Code coverage is done with the Gcov / Lcov (http://ltp.sourceforge.net/coverage/lcov.php) combo, and it is run nightly (once a day) by a Buildbot worker. The coverage results are then published at https://lcov.taler.net/ .

20.1.14. Coding Conventions#

GNU Taler is developed primarily in C, Kotlin, Python, Swift and TypeScript.

20.1.14.1. Components written in C#

These are the general coding style rules for Taler.

Baseline rules are to follow GNU guidelines, modified or extended by the GNUnet style: https://docs.gnunet.org/handbook/gnunet.html#Coding-style

20.1.14.1.1. Naming conventions#

include files (very similar to GNUnet):
- if installed, must start with “taler_” (exception: platform.h), and MUST live in src/include/
- if NOT installed, must NOT start with “taler_” and MUST NOT live in src/include/ and SHOULD NOT be included from outside of their own directory
- end in “_lib” for “simple” libraries
- end in “_plugin” for plugins
- end in “_service” for libraries accessing a service, i.e. the exchange
binaries:
- taler-exchange-xxx: exchange programs
- taler-merchant-xxx: merchant programs (demos)
- taler-wallet-xxx: wallet programs
- plugins should be libtaler_plugin_xxx_yyy.so: plugin yyy for API xxx
- libtalerxxx: library for API xxx
logging
- tools use their full name in GNUNET_log_setup (i.e. ‘taler-exchange-offline’) and log using plain ‘GNUNET_log’.
- pure libraries (without associated service) use ‘GNUNET_log_from’ with the component set to their library name (without lib or ‘.so’), which should also be their directory name (i.e. ‘util’)
- plugin libraries (without associated service) use ‘GNUNET_log_from’ with the component set to their type and plugin name (without lib or ‘.so’), which should also be their directory name (i.e. ‘exchangedb-postgres’)
- libraries with associated service) use ‘GNUNET_log_from’ with the name of the service, which should also be their directory name (i.e. ‘exchange’)
- for tools with -l LOGFILE, its absence means write logs to stderr
configuration
- same rules as for GNUnet
exported symbols
- must start with TALER_[SUBSYSTEMNAME]_ where SUBSYSTEMNAME MUST match the subdirectory of src/ in which the symbol is defined
- from libtalerutil start just with TALER_, without subsystemname
- if scope is ONE binary and symbols are not in a shared library, use binary-specific prefix (such as TMH = taler-exchange-httpd) for globals, possibly followed by the subsystem (TMH_DB_xxx).
structs:
- structs that are ‘packed’ and do not contain pointers and are thus suitable for hashing or similar operations are distinguished by adding a “P” at the end of the name. (NEW) Note that this convention does not hold for the GNUnet-structs (yet).
- structs that are used with a purpose for signatures, additionally get an “S” at the end of the name.
private (library-internal) symbols (including structs and macros)
- must not start with TALER_ or any other prefix
testcases
- must be called “test_module-under-test_case-description.c”
performance tests
- must be called “perf_module-under-test_case-description.c”

20.1.14.2. Shell Scripts#

Shell scripts should be avoided if at all possible. The only permissible uses of shell scripts in GNU Taler are:

Trivial invocation of other commands.
Scripts for compatibility (e.g. ./configure) that must run on as many systems as possible.

When shell scripts are used, they MUST begin with the following set command:

# Make the shell fail on undefined variables and
# commands with non-zero exit status.
$ set -eu

20.1.14.3. Kotlin#

We so far have no specific guidelines, please follow best practices for the language.

20.1.14.4. Python#

20.1.14.4.1. Supported Python Versions#

Python code should be written and built against version 3.7 of Python.

20.1.14.4.2. Style#

We use yapf to reformat the code to conform to our style instructions. A reusable yapf style file can be found in build-common, which is intended to be used as a git submodule.

20.1.14.4.3. Python for Scripting#

When using Python for writing small utilities, the following libraries are useful:

click for argument parsing (should be preferred over argparse)
pathlib for path manipulation (part of the standard library)
subprocess for “shelling out” to other programs. Prefer subprocess.run over the older APIs.

20.1.14.5. Swift#

Please follow best practices for the language.

20.1.14.6. TypeScript#

Please follow best practices for the language.

20.1.15. Testing library#

This chapter is a VERY ABSTRACT description of how testing is implemented in Taler, and in NO WAY wants to substitute the reading of the actual source code by the user.

In Taler, a test case is an array of struct TALER_TESTING_Command, informally referred to as CMD, that is iteratively executed by the testing interpreter. This latter is transparently initiated by the testing library.

However, the developer does not have to define CMDs manually, but rather call the proper constructor provided by the library. For example, if a CMD is supposed to test feature x, then the library would provide the TALER_TESTING_cmd_x () constructor for it. Obviously, each constructor has its own particular arguments that make sense to test x, and all constructors are thoroughly commented within the source code.

Internally, each CMD has two methods: run () and cleanup (). The former contains the main logic to test feature x, whereas the latter cleans the memory up after execution.

In a test life, each CMD needs some internal state, made by values it keeps in memory. Often, the test has to share those values with other CMDs: for example, CMD1 may create some key material and CMD2 needs this key material to encrypt data.

The offering of internal values from CMD1 to CMD2 is made by traits. A trait is a struct TALER_TESTING_Trait, and each CMD contains an array of traits, that it offers via the public trait interface to other commands. The definition and filling of such array happens transparently to the test developer.

For example, the following example shows how CMD2 takes an amount object offered by CMD1 via the trait interface.

Note: the main interpreter and the most part of CMDs and traits are hosted inside the exchange codebase, but nothing prevents the developer from implementing new CMDs and traits within other codebases.

/* Without loss of generality, let's consider the
 * following logic to exist inside the run() method of CMD1 */
...

struct TALER_Amount *a;
/**
 * the second argument (0) points to the first amount object offered,
 * in case multiple are available.
 */
if (GNUNET_OK != TALER_TESTING_get_trait_amount_obj (cmd2, 0, &a))
  return GNUNET_SYSERR;
...

use(a); /* 'a' points straight into the internal state of CMD2 */

In the Taler realm, there is also the possibility to alter the behaviour of supposedly well-behaved components. This is needed when, for example, we want the exchange to return some corrupted signature in order to check if the merchant backend detects it.

This alteration is accomplished by another service called twister. The twister acts as a proxy between service A and B, and can be programmed to tamper with the data exchanged by A and B.

Please refer to the Twister codebase (under the test directory) in order to see how to configure it.

20.1.16. User-Facing Terminology#

This section contains terminology that should be used and that should not be used in the user interface and help materials.

20.1.16.1. Terms to Avoid#

Refreshing

Refreshing is the internal technical terminology for the protocol to give change for partially spent coins

Use instead: “Obtaining change”

Charge

Charge has two opposite meanings (charge to a credit card vs. charge a battery). This can confuse users.

Use instead: “Obtain”, “Credit”, “Debit”, “Withdraw”, “Top up”

Coin

Coins are an internal construct, the user should never be aware that their balance is represented by coins of different denominations.

Use instead: “(Digital) Cash” or “(Wallet) Balance”

Consumer

Has bad connotation of consumption.

Use instead: Customer or user.

Proposal

The term used to describe the process of the merchant facilitating the download of the signed contract terms for an order.

Avoid. Generally events that relate to proposal downloads should not be shown to normal users, only developers. Instead, use “communication with merchant failed” if a proposed order can’t be downloaded.

Anonymous E-Cash

Should be generally avoided, since Taler is only anonymous for the customer. Also some people are scared of anonymity (which as a term is also way too absolute, as anonymity is hardly ever perfect).

Use instead: “Privacy-preserving”, “Privacy-friendly”

Payment Replay

The process of proving to the merchant that the customer is entitled to view a digital product again, as they already paid for it.

Use instead: In the event history, “re-activated digital content purchase” could be used. (FIXME: this is still not nice.)

Session ID

See Payment Replay.

Order

Too ambiguous in the wallet.

Use instead: Purchase

Fulfillment URL

URL that serves the digital content that the user purchased with their payment. Can also be something like a donation receipt.

Donau

Developer-internal name for the tax authority component.

Use instead: Tax authority

20.1.16.2. Terms to Use#

Auditor

Regulatory entity that certifies exchanges and oversees their operation.

Exchange Operator

The entity/service that gives out digital cash in exchange for some other means of payment.

In some contexts, using “Issuer” could also be appropriate. When showing a balance breakdown, we can say “100 Eur (issued by exchange.euro.taler.net)”. Sometimes we may also use the more generic term “Payment Service Provider” when the concept of an “Exchange” is still unclear to the reader.

Refund

A refund is given by a merchant to the customer (rather the customer’s wallet) and “undoes” a previous payment operation.

Payment

The act of sending digital cash to a merchant to pay for an order.

Purchase

Used to refer to the “result” of a payment, as in “view purchase”. Use sparingly, as the word doesn’t fit for all payments, such as donations.

Contract Terms

Partially machine-readable representation of the merchant’s obligation after the customer makes a payment.

Merchant

Party that receives a payment.

Wallet

Also “Taler Wallet”. Software component that manages the user’s digital cash and payments.

20.1.17. Developer Glossary#

This glossary is meant for developers. It contains some terms that we usually do not use when talking to end users or even system administrators.

absolute time#

method of keeping time in GNUnet where the time is represented as the number of microseconds since 1.1.1970 (UNIX epoch). Called absolute time in contrast to relative time.

aggregate#

the exchange combines multiple payments received by the same merchant into one larger wire transfer to the respective merchant’s bank account

auditor#

trusted third party that verifies that the exchange is operating correctly

bank#

traditional financial service provider who offers wire transfers between accounts

buyer#

individual in control of a Taler wallet, usually using it to spend the coins on contracts (see also customer).

close#

operation an exchange performs on a reserve that has not been emptied by withdraw operations. When closing a reserve, the exchange wires the remaining funds back to the customer, minus a fee for closing

coin#

coins are individual tokens representing a certain amount of value, also known as the denomination of the coin

contract#

formal agreement between merchant and customer specifying the contract terms and signed by the merchant and the coins of the customer

contract terms#

the individual clauses specifying what the buyer is purchasing from the merchant

customer#

individual that directs the buyer (perhaps the same individual) to make a purchase

denomination#

unit of currency, specifies both the currency and the face value of a coin, as well as associated fees and validity periods

denomination key#

(RSA) key used by the exchange to certify that a given coin is valid and of a particular denomination

deposit#

operation by which a merchant passes coins to an exchange, expecting the exchange to credit his bank account in the future using an aggregate wire transfer

dirty#

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

drain#

process by which an exchange operator takes the profits (from fees) out of the escrow account and moves them into their regular business account

empty#

a reserve is being emptied when a wallet is using the reserve’s private key to withdraw coins from it. This reduces the balance of the reserve. Once the balance reaches zero, we say that the reserve has been (fully) emptied. Reserves that are not emptied (which is the normal process) are closed by the exchange.

exchange#

Taler’s payment service operator. Issues electronic coins during withdrawal and redeems them when they are deposited by merchants

expired#

Various operations come with time limits. In particular, denomination keys come with strict time limits for the various operations involving the coin issued under the denomination. The most important limit is the deposit expiration, which specifies until when wallets are allowed to use the coin in deposit or refreshing operations. There is also a “legal” expiration, which specifies how long the exchange keeps records beyond the deposit expiration time. This latter expiration matters for legal disputes in courts and also creates an upper limit for refreshing operations on special zombie coin

fakebank#

implementation of the bank API in memory to be used only for test cases.

fee#

an exchange charges various fees for its service. The different fees are specified in the protocol. There are fees per coin for withdrawing, depositing, melting, and refunding. Furthermore, there are fees per wire transfer when a reserve is closed and for aggregate wire transfers to the merchant.

fresh#

a coin is fresh if its public key is only known to the customer

GNUnet#

Codebase of various libraries for a better Internet, some of which GNU Taler depends upon.

JSON#

JavaScript Object Notation (JSON) is a serialization format derived from the JavaScript language which is commonly used in the Taler protocol as the payload of HTTP requests and responses.

kappa#

security parameter used in the refresh protocol. Defined to be 3. The probability of successfully evading the income transparency with the refresh protocol is 1:kappa.

libeufin#

Kotlin component that implements a regional currency bank and an adapter to communicate via EBICS with European core banking systems.

link#

specific step in the refresh protocol that an exchange must offer to prevent abuse of the refresh mechanism. The link step is not needed in normal operation, it just must be offered.

master key#

offline key used by the exchange to certify denomination keys and message signing keys

melt#

step of the refresh protocol where a dirty coin is invalidated to be reborn fresh in a subsequent reveal step.

merchant#

party receiving payments (usually in return for goods or services)

message signing key#

key used by the exchange to sign online messages, other than coins

order#

offer made by the merchant to a wallet; pre-cursor to a contract where the wallet is not yet fixed. Turns into a contract when a wallet claims the order.

owner#

a coin is owned by the entity that knows the private key of the coin

planchet#

precursor data for a coin. A planchet includes the coin’s internal secrets (coin private key, blinding factor), but lacks the RSA signature of the exchange. When withdrawing, a wallet creates and persists a planchet before asking the exchange to sign it to get the coin.

privacy policy#

Statement of an operator how they will protect the privacy of users.

proof#

Message that cryptographically demonstrates that a particular claim is correct.

proposal#

a list of contract terms that has been completed and signed by the merchant backend.

purchase#

Refers to the overall process of negotiating a contract and then making a payment with coins to a merchant.

recoup#

Operation by which an exchange returns the value of coins affected by a revocation to their owner, either by allowing the owner to withdraw new coins or wiring funds back to the bank account of the owner.

refresh#

operation by which a dirty coin is converted into one or more fresh coins. Involves melting the dirty coins and then revealing so-called transfer keys.

refresh commitment#

data that the wallet commits to during the melt stage of the refresh protocol where it has to prove to the exchange that it is deriving the fresh coins as specified by the Taler protocol. The commitment is verified probabilistically (see: kappa) during the reveal stage.

refund#

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

refund transaction id#

unique number by which a merchant identifies a refund. Needed as refunds can be partial and thus there could be multiple refunds for the same purchase.

relative time#

method of keeping time in GNUnet where the time is represented as a relative number of microseconds. Thus, a relative time specifies an offset or a duration, but not a date. Called relative time in contrast to absolute time.

reserve#

accounting mechanism used by the exchange to track customer funds from incoming wire transfers. A reserve is created whenever a customer wires money to the exchange using a well-formed public key in the subject. The exchange then allows the customer’s wallet to withdraw up to the amount received in fresh coins from the reserve, thereby emptying the reserve. If a reserve is not emptied, the exchange will eventually close it.

Other definition: 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.

reveal#

step in the refresh protocol where some of the transfer private keys are revealed to prove honest behavior on the part of the wallet. In the reveal step, the exchange returns the signed fresh coins.

revoke#

exceptional operation by which an exchange withdraws a denomination from circulation, either because the signing key was compromised or because the exchange is going out of operation; unspent coins of a revoked denomination are subjected to recoup.

sharing#

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.

spend#

operation by which a customer gives a merchant the right to deposit coins in return for merchandise

terms#

the general terms of service of an operator, possibly including the privacy policy. Not to be confused with the contract terms which are about the specific purchase.

transaction#

method by which ownership is exclusively transferred from one entity

transfer key#

special cryptographic key used in the refresh protocol, some of which are revealed during the reveal step. Note that transfer keys have, despite the name, no relationship to wire transfers. They merely help to transfer the value from a dirty coin to a fresh coin

user#

any individual using the Taler payment system (see customer, buyer, merchant).

version#

Taler uses various forms of versioning. There is a database schema version (stored itself in the database, see *-0000.sql) describing the state of the table structure in the database of an exchange, auditor or merchant. There is a protocol version (CURRENT:REVISION:AGE, see GNU libtool) which specifies the network protocol spoken by an exchange or merchant including backwards-compatibility. And finally there is the software release version (MAJOR.MINOR.PATCH, see https://semver.org/) of the respective code base.

wallet#

software running on a customer’s computer; withdraws, stores and spends coins

WebExtension#

Cross-browser API used to implement the GNU Taler wallet browser extension.

wire gateway#

API used by the exchange to talk with some real-time gross settlement system (core banking system, blockchain) to notice inbound credits wire transfers (during withdraw) and to trigger outbound debit wire transfers (primarily for deposits).

wire transfer#

a wire transfer is a method of sending funds between bank accounts

wire transfer identifier#

Subject of a wire transfer from the exchange to a merchant; set by the aggregator to a random nonce which uniquely identifies the transfer.

withdraw#

operation by which a wallet can convert funds from a reserve to fresh coins

zombie#

coin where the respective denomination key is past its deposit expiration time, but which is still (again) valid for an operation because it was melted while it was still valid, and then later again credited during a recoup process

20.1.18. Developer Tools#

This section describes various internal programs to make life easier for the developer.

20.1.18.1. taler-harness#

taler-harness deployment gen-coin-config is a tool to simplify Taler configuration generation.

taler-harness deployment gen-coin-config [-min-amount**=‌VALUE] [-max-amount**=‌VALUE]

General Developer Manual

Contents

20.1. General Developer Manual#

20.1.1. Project Overview#

20.1.2. Fundamentals#

20.1.2.1. Versioning#

20.1.2.2. Tagging and Package Versioning#

20.1.2.3. Testing Tools#

20.1.2.4. Manual Testing Database Reset#

20.1.2.5. Bug Tracking#

20.1.2.6. Code Repositories#

20.1.2.7. Committing code#

20.1.2.8. Observing changes#

20.1.2.9. Code generator usage policy#

20.1.2.10. Communication#

20.1.2.11. What to put in bootstrap#

20.1.3. Debian and Ubuntu Repositories#

20.1.3.1. Nightly Repositories#

20.1.4. Taler Deployment on gv.taler.net#

20.1.4.1. DNS#

20.1.4.2. User Acccounts#

20.1.5. Demo Upgrade Procedure#

20.1.5.1. Tagging components#

20.1.6. Environments and Builders on taler.net#

20.1.6.1. Buildbot implementation#

20.1.6.2. Test builder#

20.1.6.3. Wallet builder#

20.1.6.4. Documentation Builder#

20.1.6.5. Website Builder#

20.1.6.6. Code coverage#

20.1.6.7. Producing auditor reports#

20.1.6.8. Database schema versioning#

20.1.7. QA Plans#

20.1.7.1. Taler 1.0 QA Plan#

20.1.7.1.1. Wallet Platforms#

20.1.7.1.2. Running Deployments#

20.1.7.1.3. Check UX Flows#

20.1.7.1.4. Regio Deployment#

20.1.7.1.5. Continuous Integration#

20.1.7.1.6. Debian Repository#

20.1.7.1.7. GNU Release#

20.1.8. Releases#

20.1.8.1. GNU Taler Release Checklist#

20.1.8.2. Release Process#

20.1.8.3. Tagging#

20.1.8.4. Database for tests#

20.1.8.5. Exchange, merchant#

20.1.8.6. Wallet WebExtension#

20.1.8.7. Upload to GNU mirrors#

20.1.8.8. Creating Debian packages#

20.1.9. Continuous integration#

20.1.10. Internationalisation#

20.1.11. iOS Apps#

20.1.11.1. Building Taler Wallet for iOS from source#

20.1.11.1.1. Compatibility#

20.1.11.1.2. Building#

20.1.12. Android Apps#

20.1.12.1. Android App Nightly Builds#

20.1.12.2. Building apps from source#

20.1.12.3. Update translations#

20.1.12.4. Release process#

20.1.12.4.1. F-Droid#

20.1.12.4.2. Google Play#

20.1.13. Code Coverage#

20.1.14. Coding Conventions#

20.1.14.1. Components written in C#

20.1.14.1.1. Naming conventions#

20.1.14.2. Shell Scripts#

20.1.14.3. Kotlin#

20.1.14.4. Python#

20.1.14.4.1. Supported Python Versions#

20.1.14.4.2. Style#

20.1.14.4.3. Python for Scripting#

20.1.14.5. Swift#

20.1.14.6. TypeScript#

20.1.15. Testing library#

20.1.16. User-Facing Terminology#

20.1.16.1. Terms to Avoid#

20.1.16.2. Terms to Use#

20.1.17. Developer Glossary#