From 465990bc7b5746b31660e71a098440872acd9fc7 Mon Sep 17 00:00:00 2001
From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Mon, 28 Mar 2016 01:01:06 +0200
Subject: [PATCH] Issue marker requesting security considerations section

---
 .gitignore                | 1 +
 specs/paymentrequest.html | 8 ++++++++
 2 files changed, 9 insertions(+)
 create mode 100644 .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 00000000..62c89355
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+.idea/
\ No newline at end of file
diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index f0734b71..9460b9c2 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -978,6 +978,14 @@ <h2>PaymentRequestUpdateEvent</h2>
       Accept-Language headers, etc.)
     </p>
 
+
+    <p class="issue" data-number="55" title="Add section on security considerations">
+      The spec should indicate how data might be passed securely through the API using
+      mechanisms such as field level encryption and message signing. While these may not
+      be standardised a reference to the payment method specifications would be appropriate
+      as well as some examples of how those specifcations might implement secure messaging.
+    </p>
+
     <section>
       <h2>Algorithms</h2>