-
Notifications
You must be signed in to change notification settings - Fork 0
Pay Link
- Prologue
- Characteristics
- Requirements and restrictions
-
Scenarios
- Baseline scenario 1: Open Pay link on mobile or desktop
- Baseline scenario 2: The user pays the transaction
- Baseline scenario 3: User has no MultiCash
- Baseline scenario 4: No transactions found after payment
- Baseline scenario 5: Transaction not confirmed
- Alternative scenario 1: Open main website
- Error scenario 1: Open Pay link with wrong information
MultiCash Pay provides a simple solution for users to use received MultiCash Pay links that look like this:
https://pay.multicash.io/{receiveAddress}?tag={receiveTag}&amount={receiveAmount}&label={paymentLabel}
These links are usually generated by applications like the MultiCash mobile app to request a payment from other users.
The service lets users pay them as easy as possible by either showing a QR code in a browser to be scanned by our Mobile app, by helping users setup their mobile app or by opening the application directly from the device if it has a working and setup mobile app. By also showing feedback on this webpage for desktop users about a payment being received we provide a seamless solution and make users feel confident the transaction was successful.
Characteristic | Description |
---|---|
Actor | User |
Reason | Users need to have easy and understandable ways to send each other or businesses MCX |
Related use cases |
- The pay link webpage with transaction proposal information must be accessible using a link with the format:
https://pay.multicash.io/{receiveAddress}?tag={receiveTag}&amount={receiveAmount}&label={paymentLabel}
Precondition(s):
- User opens a MultiCash Pay link on their mobile phone or on a desktop computer
Scenario description:
- If the MultiCash mobile app is install on their mobile device the MultiCash mobile app will be opened automatically and this scenario will end here. Otherwise the (mobile) browser will be opened.
- The request gets validated with the incoming data:
On error proceed to E1
Parameter * address Query parameter * amount * tag * label (optional)
- The page gets served with the given address, amount, tag and optional label
Postcondition(s):
- The user is served a page with all transaction information and a QR which can be scanned by MultiCash mobile app. The user also has the possibility to choose a "Get Started with MultiCash" option.
Precondition(s):
- User pays the MultiCash Pay link
Scenario description:
- The service checks every 5 seconds if a transaction with the known transaction parameters (address, amount) has been created after the page load time.
- If a transaction that matches is found the user is provided with feedback.
On timeout of 5 minutes the check gets canceled and the user proceeds to scenario B4
- The services keeps checking until at least 1 confirmation.
On timeout of 5 minutes after finding the new transaction without any new confirmation the user proceeds to scenario B5
- If the transaction is confirmed 1 time the user is provided with feedback the transaction was successfully completed.
Postcondition(s):
- The user is served with the successfully completed transaction page.