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
- 2aa5774601b038d554226c2a3ea959817f70457d6aac859aaf55006acf3330e3
- request
- e4217cf180b3a7e7e3cbb122359600028408b72c8a92ff963010d5dae0f98ea9
- transaction
- 0439682aaf8bd1595eb0dedb6fcd4066f9c124f90bb80e435d77f04fe4362983computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72206
the chainentry 72206
- sealed to the entry before
- 16faf715960dd26bd86a0ddcf8ffd71e226acd73c0a9f0d35deea7dfe3ea0a22
- this leaf
- f6fb5efea0d987515ada9c85190f9d9e1c160a2cde212498880bfa7db5306598
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fJM7dhK1wBxgKETZwDGXgkxzTwuAr8rkin5cobSqeHb2EllSuhP7n6gVdeiS/RtSj4iQJqivQPe+SylK0cd4AA==