From f5957f10075acf7a6149b89f503ac36fad1d19f6 Mon Sep 17 00:00:00 2001 From: Jeremy Klein Date: Sun, 18 Feb 2024 17:31:05 -0800 Subject: [PATCH] Move back kycstatus because it's still needed in the lnurlpresponse --- umad-04-lnurlp-response.md | 1 + umad-06-payreq-response.md | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/umad-04-lnurlp-response.md b/umad-04-lnurlp-response.md index 3bad743..72a6908 100644 --- a/umad-04-lnurlp-response.md +++ b/umad-04-lnurlp-response.md @@ -50,6 +50,7 @@ The full structure of the LNURLP response is: // UMA-specific authentication and compliance info. "compliance" { "isSubjectToTravelRule": boolean, // true if VASP2 needs travel rule info + "kycStatus": KycStatus, // [enum] KYC state indicating whether the receiver is a KYC'd customer of VASP2. "signature": string, // hex encoded "signatureNonce": string, "signatureTimestamp": number, // secs since epoch diff --git a/umad-06-payreq-response.md b/umad-06-payreq-response.md index d52f949..dcb6a81 100644 --- a/umad-06-payreq-response.md +++ b/umad-06-payreq-response.md @@ -32,8 +32,6 @@ The full structure of the LNURLP response is: }, "payeeData": { "compliance": { - // [enum] KYC state indicating whether the receiver is a KYC'd customer of VASP2. - "kycStatus": KycStatus, // Public key of the recipient node for pre-screening. "nodePubKey": string, // A list of the expected UTXOs over which the receiver may receive the transaction (receiver's channels).