commit 26e8662e519e26717c06f2af870cc2c585a2f461
parent ef679017059f0a1f297e917531aad657a94609fb
Author: MS <ms@taler.net>
Date: Tue, 6 Oct 2020 15:13:45 +0200
making payments with nexus
Diffstat:
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst
@@ -158,6 +158,10 @@ list of transactions, and making a payment.
Request history of transactions
===============================
+..
+ FIXME: explain why requesting the history
+ goes through these two-phases.
+
It is first needed to tell Nexus to download the latest news
from the bank, and then ask it again to return the results.
@@ -189,7 +193,42 @@ client can ask to actually **see** the transactions:
Make a payment
==============
-TBD.
+..
+ FIXME: explain why payments go through these two-phases.
+
+Payments pass through two phases: preparation and submission.
+
+The following command prepares a payment:
+
+.. code-block:: shell
+
+ libeufin-cli \
+ accounts \
+ prepare-payment \
+ --account-name $CUSTOM_RENAMING_FOR_ACCOUNT \
+ --credit-iban $IBAN_TO_SEND_MONEY_TO \
+ --credit-bic $BIC_TO_SEND_MONEY_TO \
+ --credit-name $LEGAL_ENTITY_RECEIVING_THE_PAYMENT \
+ --payment-amount $AMOUNT \ # NOTE THIS.
+ --payment-subject $SUBJECT \
+ --nexus-user-id $NEXUS_USER \
+ --nexus-password $NEXUS_PASSWORD \
+ $NEXUS_URL
+
+The previous command should return a value (``$UUID``) that uniquely
+identifies the prepared payment in the Nexus system. It'll be needed
+in the next step, to **send the payment instructions to the bank**:
+
+.. code-block:: shell
+
+ libeufin-cli \
+ accounts \
+ submit-payment \
+ --account-name $CUSTOM_RENAMING_FOR_ACCOUNT \
+ --payment-uuid $UUID \
+ --nexus-user-id $NEXUS_USER \
+ --nexus-password $NEXUS_PASSWORD \
+ $NEXUS_URL
Restore the backup
==================
