why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 96ee6bc48baa4ef6121faf2584b6a620f696401562a8a71e8641942daff9430c
- request
- 88467df34ee1dd4906120f879b471f9c8978f2396400abd2d12f109720965568
- transaction
- f0d72edf1df1e6e37f0024e66acdbdae8c9973f688d6f8b4b798abc77ba97826computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60632
the chainentry 60632
- sealed to the entry before
- 3203596f72232cc6ee9d641e2b3af65d3af8e9b391ecfd7a6f36cc16d6b93eea
- this leaf
- 63b1c37902060443c9392275fdb027d337fa2ee2851f613d5238d3027a7f4136
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SVJFNXfxmmeLChJ/09oNW8lPW6rA9gtuXse7QUpqm3axC72j0Zmya5kqnenqD5j2UWgOLZLDz8yp6LiFZa/CDw==