taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 0f9a3b59aa49f46771c10a3d30528034ad49b3a8
parent 788d4aaf34d46104e296d5050db10a5d7d1feced
Author: MS <ms@taler.net>
Date:   Mon,  5 Oct 2020 18:56:53 +0200

libeufin howto, more instructions

Diffstat:
Mlibeufin/nexus-howto.rst | 35+++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+), 0 deletions(-)

diff --git a/libeufin/nexus-howto.rst b/libeufin/nexus-howto.rst @@ -122,8 +122,43 @@ This step is needed to let the user pick a custom name for such accounts. --nexus-bank-account-id $CUSTOM_RENAMING_FOR_ACCOUNT \ $NEXUS_URL +Once a Nexus user imported a bank account (``$CUSTOM_RENAMING_FOR_ACCOUNT``) +under a certain connection (``$NEXUS_BANK_CONNECTION_NAME``), it is possible +to accomplish the usual operations for any bank account: asking for the +list of transactions, and making a payment. + Request history of transactions =============================== +It is first needed to tell Nexus to download the latest news +from the bank, and then ask it again to return the results. + +This command asks Nexus to *download the latest bank statements*: + +.. code-block:: shell + + ./libeufin-cli \ + accounts \ + fetch-transactions \ + --nexus-user-id $NEXUS_USER \ + --nexus-password $NEXUS_PASSWORD \ + --account-name $CUSTOM_RENAMING_FOR_ACCOUNT \ + $NEXUS_URL + +Once Nexus stored all the information in the database, the +client can ask to actually **see** the transactions: + +.. code-block:: shell + + ./libeufin-cli + accounts \ + transactions \ + --nexus-user-id $NEXUS_USER \ + --nexus-password $NEXUS_PASSWORD \ + --account-name $CUSTOM_RENAMING_FOR_ACCOUNT \ + $NEXUS_URL + Make a payment ============== + +TBD.