diff --git a/docu/Concepts/TechnicalRequirements/UC_X-Com-Tx_per_Link.md b/docu/Concepts/TechnicalRequirements/UC_X-Com-Tx_per_Link.md index 3c9083f3e..626703438 100644 --- a/docu/Concepts/TechnicalRequirements/UC_X-Com-Tx_per_Link.md +++ b/docu/Concepts/TechnicalRequirements/UC_X-Com-Tx_per_Link.md @@ -16,7 +16,7 @@ After a user has created a `redeem-Link` to send an other user an amount of grad example: `https://gdd.gradido.net`/redeem/`3a5839be29f1` -In consequence of these technical details the transaction-link is created, the recipient will be routed on activation to the community of the sender. +In consequence of these technical details the transaction-link is created, the recipient will be routed on activation to the community of the sender. With receiving a redeem-link request the payload of this link will be validated: @@ -67,22 +67,34 @@ After confirming the community-selection the system will check if the selected c In the first case the system goes on with the local login or registration page for a local `redeem-link activation`. -In case of the recipient community will be a foreign community, the system has to prepare a request with a _securitykey_ to invoke on the foreign community the login- or register-page. +In case of the recipient community will be a foreign community, the system has to prepare a request with a _Disbursement-JWT-Token_ as parameter to invoke on the foreign community the _disbursement process_ by following the pattern: `community-url of receiver-community`/redeem/`` the receiving community will show the following page with content from the ``. + +![](./image/redeemlink-page_without-comunity-selection.png) + +There will no additional community-selection component exist, as it is shown on the sender-community before - see chapter Community-Selection above. + +After the user finished the login or registration on the receiver community successfully the receiver-gradidoID for the disbursement transaction is known. To process the _disbursement process_ the backend offers the graphql query: + +``` +TransactionResolver.disburse { jwt-token } :Promise boolean +``` + +with the _disbursement-jwt-token_ as parameter and returns `true` in case of successful invocation, otherwise `false`. + +The backend of the receiver community will prepare the parameters for a disbures-request invocation against the _sender-community_. diff --git a/docu/Concepts/TechnicalRequirements/image/redeemlink-page_without-comunity-selection.png b/docu/Concepts/TechnicalRequirements/image/redeemlink-page_without-comunity-selection.png index 7a54a0415..4c96d2821 100644 Binary files a/docu/Concepts/TechnicalRequirements/image/redeemlink-page_without-comunity-selection.png and b/docu/Concepts/TechnicalRequirements/image/redeemlink-page_without-comunity-selection.png differ