-more work on iban logic

1 files changed, 11 insertions, 6 deletions

diff --git a/doc/sphinx/reducer.rst b/doc/sphinx/reducer.rst
index e1ca9ba..320db48 100644
--- a/doc/sphinx/reducer.rst
+++ b/doc/sphinx/reducer.rst
@@ -1641,6 +1641,8 @@ that applications must all handle. States other than ``solved`` are:
             "TXYKGE1SJZHJ4M2FKSV1P2RZVNTHZFB9E3A79QE956D3SCAWXPK0": {
               "state": "external-instructions",
               "method": "iban",
+              "async": true, // optional
+              "answer_code": 987654321, // optional
               "details": {
                 "...": "..."
               }
@@ -1648,7 +1650,12 @@ that applications must all handle. States other than ``solved`` are:
           }
         }
 
-    The specific instructions depend on the ``method``.
+    If "async" is "true", then the client should
+    poll for the challenge being satisfied using
+    the "answer_code" that has been provided.
+
+    The specific instructions on how to satisfy
+    the challenge depend on the ``method``.
     They include:
 
       - **iban**: The user must perform a wire transfer from their account to the Anastasis provider.
@@ -1659,14 +1666,12 @@ that applications must all handle. States other than ``solved`` are:
             "challenge_amount": "EUR:1",
             "credit_iban": "DE12345789000",
             "business_name": "Data Loss Incorporated",
-            "wire_transfer_subject": 987654321
+            "wire_transfer_subject": "Anastasis 987654321"
           }
 
         Note that the actual wire transfer subject must contain both
-        the numeric ``wire_transfer_subject`` given above as well as
-        the string ``Anastasis``. Thus, when generating human-readable
-        instructions from the above, the display output should be
-        ``Anastasis 987654321``.
+        the numeric ``answer_code`` as well as
+        the string ``Anastasis``.
 
 **poll:**