-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# UMAD-11 Request | ||
|
||
UMA request is a way to deliver UMA invoices to sending wallets. Such as deep/universal links on | ||
Check failure on line 3 in umad-11-request.md GitHub Actions / markdown-lintTrailing spaces
|
||
mobile, notification, etc. | ||
|
||
## Request for non-specified sender | ||
|
||
To deliver a UMA invoice to a sending wallet, the receiver can create a UMA invoice, and then | ||
deliver the encoded UMA invoice string to the sending wallet. | ||
|
||
The invoice string should be delivered using the following URL pattern: | ||
|
||
```raw | ||
uma://<invoice_string> | ||
``` | ||
|
||
This can be displayed as a QR code, or a deep link on mobile. The sending wallet should register | ||
the `uma` scheme to handle the UMA invoice string. | ||
|
||
## Request for specified sender | ||
|
||
To deliver a UMA invoice with a specified sender, the receiver can create a UMA invoice, and then | ||
directly send the UMA invoice to the sending VASP. | ||
|
||
The request URL should be defined in the uma-configuration scheme (See UMAD-10 for details) as: | ||
|
||
```raw | ||
"uma_request_endpoint": "https://vasp1.com/path/to/request/url" | ||
``` | ||
|
||
The sending VASP should implement the request endpoint as a POST endpoint that accepts the UMA | ||
Check failure on line 31 in umad-11-request.md GitHub Actions / markdown-lintTrailing spaces
|
||
invoice. The payload should be a JSON object with the following fields: | ||
|
||
```raw | ||
{ | ||
"invoice": "<UMA invoice string>" | ||
} | ||
``` | ||
|
||
Once sending VASP receives the UMA invoice, it should notify the sending wallet to confirm the payment. | ||
Check failure on line 40 in umad-11-request.md GitHub Actions / markdown-lintFiles should end with a single newline character
|