From effcbec85dd2a4e3b295be1d7e61c78e6aa940db Mon Sep 17 00:00:00 2001
From: Jeremy Klein <jklein24@gmail.com>
Date: Tue, 14 Nov 2023 17:22:35 -0800
Subject: [PATCH] Fix some incorrect labels in umad-04

This doc was slightly mis-aligned with all of the SDK implementations. Correcting field names and types.
---
 umad-04-lnurlp-response.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/umad-04-lnurlp-response.md b/umad-04-lnurlp-response.md
index ac2c0ee..0020fcd 100644
--- a/umad-04-lnurlp-response.md
+++ b/umad-04-lnurlp-response.md
@@ -46,9 +46,10 @@ The full structure of the LNURLP response is:
   "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,
-    "nonce": string,
-    "timestamp": string // secs since epoch
+    "signature": string, // hex encoded
+    "signatureNonce": string,
+    "signatureTimestamp": number // secs since epoch
+    "receiverIdentifier": string // The identity of the receiver at VASP2
   },
   "umaVersion": "1.0", // The UMA protocol version that will be used for this transaction.
   "tag": "payRequest",