taler-merchant-setup-reserve - setup reserve for tipping
taler-merchant-setup-reserve [-A USERNAME:PASSWORD | –auth=USERNAME:PASSWORD] [-a VALUE | –amount=VALUE] [-C CERTFILE | –cert=CERTFILE] [-c FILENAME | –config=FILENAME] [-e URL | –exchange-url=URL] [-h | –help] [-k KEYFILE | –key=KEYFILE] [-L LOGLEVEL | –loglevel=LOGLEVEL] [-l FILENAME | –logfile=FILENAME] [-m URL | –merchant-url=URL] [-p KEYFILEPASSPHRASE | –pass=KEYFILEPASSPHRASE] [-t CERTTYPE | –type=CERTTYPE] [-w METHOD | –wire-method=METHOD] [-v | –version]
taler-merchant-setup-reserve is a command-line tool to setup a reserve (creating the private reserve key) and obtaining the wire transfer information from the exchange needed to fill the reserve.
USERNAME
and PASSWORD
for HTTP client authentication.
The “:” must be present as a separator.
Note that this form of authentication has nothing to do with the TLS client
certificate authentication supported with the -C
, -k
and -p
options.
The PASSWORD
given to this option is given to the server!CERTFILE
contains a TLS client certificate to be used to
authenticate the client. See also -t
.FILENAME
.URL
for the exchange base URL.
This is the exchange where the reserve will be created.
The currency used in the amount specification must be offered by this exchange.KEYFILE
contains a TLS client private key to be used to
authenticate the client. See also -p
and -C
.DEBUG
, INFO
,
WARNING
, ERROR
.URL
as the merchant base URL.
Should include the path to the instance if the reserve is to be
created for a non-default instance.KEYFILEPASSPHRASE
is to be used to decrypt the KEYFILE.
See also -k
. Not to be confused with -A
.
The KEYFILEPASSPHRASE
given here is only used locally to decrypt the KEYFILE.CERTTYPE
.
Default is PEM
. See also -C
.iban
or x-taler-bank
.taler-merchant-dbinit(1), taler.conf(5)
Report bugs by using https://bugs.taler.net/ or by sending electronic mail to <taler@gnu.org>.