From a7c8554eeb6dfeb6e15b51984378c30ec31bcff3 Mon Sep 17 00:00:00 2001
From: Jeff Vandrew Jr <43861226+JeffVandrewJr@users.noreply.github.com>
Date: Mon, 11 Mar 2019 16:55:22 -0400
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fa0cced..dc5d08a 100644
--- a/README.md
+++ b/README.md
@@ -37,7 +37,7 @@ client = BTCPayClient.create_client(host='https://btcpay.example.com', code=<pai
 
 You'll probably only ever need the `create_invoice` and `get_invoice` methods, but the client object also has other methods, such as those for getting and setting custom rate information.
 
-The `get_invoice` method is very important. When BTCPay sends a payment notification, it is unsigned and insecure. This is necessary to maintain Bitpay compatibility. You therefore cannot rely upon the data transmitted in the payment notification.
+The `get_invoice` method is very important. When BTCPay sends a payment notification (described [here in Bitpay's API docs](https://bitpay.com/docs/create-invoice), it is unsigned and insecure. Being unsigned and insecure is necessary to maintain compatibility with software originally designed for Bitpay. You therefore cannot rely upon the data transmitted in the payment notification.
 
 Instead, take the `invoiceId` from the payment notification, and use it to securely fetch the paid invoice data from BTCPay using `get_invoice`.