commit 602687cdc761f53ba7104ea5858ab25aa4ccf577
parent 57790c91851c8d75164d09eaacaa985e4949c7bc
Author: Christian Grothoff <christian@grothoff.org>
Date: Thu, 19 Feb 2026 19:24:55 +0100
minor edits
Diffstat:
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/pos-integration.rst b/pos-integration.rst
@@ -90,10 +90,18 @@ For the integrated onboarding, the steps for the merchant are:
info, etc. via the respective endpoints). This is done using
administrative credentials on the merchant backend.
* The PoS provider transmits KYC information for the new merchant to the Taler
- exchange.
+ exchange (this will require a new endpoint to be implemented that does
+ not yet exist, as well as an agreement between the exchange operator
+ and the PoS terminal provider, for example to include the exchange
+ operator terms of service in the onboarding of the PoS terminal provider).
+ We anticipate that this will be done by POSTing (possibly multiple times)
+ the KYC data in JSON format to an authenticated endpoint. The best
+ options for sharing access to large files, such as onboarding videos,
+ will need to be discussed.
* PoS is now ready to accept Taler payments.
+
Payments
--------
@@ -150,4 +158,3 @@ configured contact method(s) such as SMS or E-Mail.
Furthermore, the :http:get:`[/instances/$INSTANCE]/private/kyc` endpoint may be requested by the PoS terminal
to request information about the KYC status (per merchant bank account and
Taler Exchange).
-
