@depay/widgets 8.0.3 → 8.0.5

package/README.md

@@ -364,33 +364,9 @@ Those values are supposed to be set by your backend not the widget nor the front
 
 Make sure you read the [Payment Tracking API](https://depay.com/documentation/api#payments) for further details on how to integrate payment tracking.
 
-Payment tracking requests will be attempted up to 3 times by the widget and will display "Payment tracking failed!" to the user if the widget was not able to start payment tracking via the given endpoint after 3 attempts.
+Payment tracking requests will be attempted indefinitely. After 2 minutes a warning dialog will be presented to users asking them to ensure an internet connection so that the payment tracking can be performed.
 
-A failed payment tracking will also call the [error callback](#error) with `{code: "TRACKING_FAILED"}`.
-
-##### Asynchronous Validation
-
-For improving user experience, we recommend performing payment validation asynchronously as in certain situation in can take up to multiple minutes.
-
-You can configure the widget to track/validate the payment asynchronously:
-
-```javascript
-DePayWidgets.Payment({
-
-  track: {
-    endpoint: '/track',
-    async: true
-  }
-})
-```
-
-Which will release the user right after the payment has been confirmed on the user's machine.
-
-It still tracks and validates the payment asynchronously and calls back your endpoints as soon as it has been validated.
-
-This allows you to release the user immediately, showing him some confirmation and reconfirming his payment in an asynchronous step (like a notification or email).
-
-##### Additional Polling
+##### Polling
 
 In order to ensure a 100% coverage that users are released and forwarded within your payment flow, you will need to implement polling in addition to tracking.
 
@@ -501,7 +477,7 @@ DePayWidgets.Payment({
 
 A function that will be called once the payment has been sent to the network (but still needs to be mined/confirmed).
 
-The widget will call this function with a transaction as single argument (see: [depay-web3-wallets](https://github.com/depayfi/depay-web3-wallets#transaction) for more details)
+The widget will call this function with a transaction as single argument (see: [depay-web3-wallets](https://github.com/depayfi/depay-web3-wallets#transaction) for more details about the structure)
 
 ```javascript
 DePayWidgets.Payment({
@@ -1796,7 +1772,18 @@ BODY
   }
 ```
 
-The `/login` endpoint needs to recover the address for `message` and `signature` and needs to return it in the response:
+The `/login` endpoint needs to recover the address for `message` and `signature`.
+
+e.g. your backend could use node + ethers.js to recover the signature
+
+```javascript
+const ethers = require('ethers')
+const hashedMessage = ethers.utils.hashMessage(inputs.message)
+const address = ethers.utils.recoverAddress(hashedMessage, inputs.signature)
+return address
+```
+
+make sure you return the recovered address back to the widget:
 
 ```
 POST /login
@@ -1804,6 +1791,7 @@ RESPONSE
   "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
 ```
 
+
 Which will resolve the `DePayWidgets.Login` request to the resolved account:
 
 ```javascript