LIBEUFIN-NEXUS(1)

πŸ“¦ version 1.3.0, in nixos 26.05, nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

okay bestie, welcome to libeufin-nexus β€” the service that interfaces to various bank access APIs ✨ (this is the libeufin-nexus(1) page from the GNU Taler manual, and yes it's a whole vibe).


🌸 SYNOPSIS 🌸

libeufin-nexus [-h | --help] [--version] COMMAND [ARGS...]

Subcommands: dbinit, ebics-setup, ebics-submit, ebics-fetch, serve,
initiate-payment, manual, list, config

πŸ’– DESCRIPTION πŸ’–

libeufin-nexus is a program that provides a service to interface to various bank access APIs. that's the whole thing, that's the assignment 🫢

Its options are as follows:

  • -h | --help β€” Print short help on options.
  • –version β€” Print version information.

The interaction model is as follows:

  • Configure the database with commands dbinit.
  • Setup EBICS access with commands ebics-setup. Setting the access means to share the client keys with the bank and downloading the bank keys.
  • After a successful setup, the subcommands ebics-submit and ebics-fetch can be run to respectively send payments and download the bank account history.
  • Start the HTTP server with command serve. Let this run in a shell, writing logs to stderr.

The following sections describe each command in detail. buckle up πŸŽ€

🧚 dbinit

This command defines the database schema for LibEuFin Nexus. It is mandatory to run this command before invoking the ebics-setup or serve commands. like, do not skip this one, fr fr 😭

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -r | --reset β€” Reset database (DANGEROUS: All existing data is lost). πŸ‘‘πŸ’€
  • -h | --help β€” Print short help on options.
⚠️ -r / --reset is literally the "delete everything" button. The manual says DANGEROUS: All existing data is lost. All of it. gone. so maybe don't. πŸ’€

πŸ”₯ ebics-setup

This command creates the client keys, if they aren't found already on the disk, and sends them to the bank if they were not sent yet. In case of sending, it ejects the PDF document that contains the keys fingerprints, so that the user can send it to the bank to confirm their keys. πŸ“„βœ¨

The process continues by checking if the bank keys exist already on disk, and proceeds with downloading them in case they are not. It checks then if the bank keys were accepted by the user; if yes, the setup terminates, otherwise it interactively asks the user to mark the keys as accepted. By accepting the bank keys, the setup terminates successfully. πŸŽ€ slay.

It is mandatory to run this command before invoking the ebics-fetch or ebics-submit commands.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --force-keys-resubmission β€” Resubmits all the keys to the bank.
  • --auto-accept-keys β€” Accepts the bank keys without interactively asking the user.
  • --generate-registration-pdf β€” Generates the PDF with the client keys fingerprints, if the keys have the submitted state. That's useful in case the PDF went lost after the first submission and the user needs a new PDF. 🫢
  • --debug-ebics β€” Log EBICS transactions steps and payload at log_dir.
  • -h | --help β€” Print short help on options.

πŸ’Έ ebics-submit

This subcommand submits EBICS files to the bank. It submits pending outgoing payments. Outgoing payment status is fetched by ebics-fetch.

Submits are executed at 'FREQUENCY'.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --transient β€” Execute once and return, ignoring the 'FREQUENCY' configuration value.
  • --debug-ebics log_dir β€” Log EBICS transactions steps and payload at log_dir.
  • -h | --help β€” Print short help on options.

🌈 ebics-fetch

This subcommand fetches EBICS files from the bank. Incoming payments are recorded and the status of outgoing payments is updated. πŸ’…

If ACCOUNT_TYPE is exchange, incoming payments with an invalid Taler subject are bounced. Bounces are submitted by ebics-submit.

Fetches of new documents are executed at 'FREQUENCY' or any time a real-time EBICS notification is received. Every day, a checkpoint is performed, during which all documents since the last checkpoint are fetched. πŸ¦‹

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --transient β€” Execute once and return, ignoring the 'FREQUENCY' configuration value.
  • --pinned-start YYYY-MM-DD β€” Only supported in --transient mode, this option lets specify the earliest timestamp of the downloaded documents.
  • --peek β€” Only supported in --transient mode, do not consume fetched documents.
  • --checkpoint β€” Only supported in --transient mode, run a checkpoint.
  • --debug-ebics log_dir β€” Log EBICS transactions steps and payload at log_dir.
  • -h | --help β€” Print short help on options.
🫢 heads up: --pinned-start, --peek and --checkpoint are only supported in --transient mode. no cap.

πŸ‘‘ serve

This command starts the HTTP server. main character energy tbh 🌟

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --check β€” Check whether an API is in use (if it's useful to start the HTTP server). Exit with 0 if at least one API is enabled, otherwise 1.
  • -h | --help β€” Print short help on options.

πŸŽ€ initiate-payment

This subcommand initiates an outgoing payment. The pending payment is stored in the database and will be performed the next time ebics-submit run. πŸ’Έ

It takes one argument, the creditor IBAN payto URI, which must contain a 'receiver-name' and may contain an 'amount' and a 'message' if they have not been defined using CLI options.

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --amount AMOUNT β€” The amount to transfer, payto 'amount' parameter takes the precedence.
  • --subject TEXT β€” The payment subject, payto 'message' parameter takes the precedence.
  • --request-uid TEXT β€” The payment request UID, will be randomly generated if missing. ✨
  • -h | --help β€” Print short help on options.

πŸ“ manual

Manual management commands.

Its options are as follows:

  • -h | --help β€” Print short help on options.

Subcommands: export, import, status, ack

πŸ“€ manual export

Export pending batches as pain001 messages.

It takes one argument, the path where to write the zip export.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

πŸ“₯ manual import

Import EBICS camt files.

It takes multiple arguments, the paths to XML files to import.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

πŸ”„ manual status

Change batches or transactions status.

It takes four arguments: the element kind, the element id, the new status and an optional status message.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

βœ… manual ack

Manually acknowledge the outgoing transaction for submission.

It takes many transactions as arguments.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

🧾 list

List nexus transactions.

Its options are as follows:

  • -h | --help β€” Print short help on options.

Subcommands: incoming, outgoing, initiated

πŸ“© list incoming

List incoming transactions.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

πŸ“¨ list outgoing

List outgoing transactions.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

🌟 list initiated

List initiated transactions.

Its options are as follows:

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • --ack | --awaiting-ack β€” Only list transactions awaiting manual acknowledgement.
  • -h | --help β€” Print short help on options.

βš™οΈ config

This command inspect or change the configuration.

  • -h | --help β€” Print short help on options.

Subcommands: get, dump, pathsub

πŸ” config get

This command lookup config value.

It takes two arguments, the section name and the option name.

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -f | --filename β€” Interpret value as path with dollar-expansion.
  • -h | --help β€” Print short help on options.

πŸ—‚οΈ config dump

This command dump the configuration.

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

πŸ›€οΈ config pathsub

This command substitute variables in a path.

It takes one argument, a path expression.

  • -c | --config config_file β€” Specifies the configuration file.
  • -L | --log LOGLEVEL β€” Configure logging to use LOGLEVEL.
  • -h | --help β€” Print short help on options.

πŸ‘€ SEE ALSO πŸ‘€

libeufin-nexus.conf(5) β€” go read the config page too bestie, it's giving lore πŸ¦‹

πŸ’€ BUGS πŸ’€

Report bugs by using https://bugs.taler.net or by sending electronic mail to <taler@gnu.org>. please do, they wanna hear from you 🫢

✨ AUTHOR ✨

GNU Taler contributors πŸ‘‘

2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)


and that's the whole page, bestie! πŸ“ this was version 1.0, dated Dec 22, 2025 β€” go forth and interface with those bank APIs, you're gonna slay πŸ’…πŸŒˆ

πŸ“¦ where this page comes from