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
- cbf5141607edbdcbc541a9c10f87e8f7aaabfdc42c31eb780232f03bdd2a7340
- request
- 5b3cc78876c42b8a964468a01a0ceba15915823f9b49d61f3cdd52a5c2ace455
- transaction
- e4727fa3fb25e498fdb7a5dcf8a73dd033d304820ccb2816bdf7c458ad7544a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2180
the chainentry 2180
- sealed to the entry before
- cfcef583b4bceebf524d5d498d687e7426d0acddedff4dd41a14e6fa504eb464
- this leaf
- f655c79a063f0e297a1961529b26cfc2dc9bff4e905f8eb5b15f79a9350506e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k/EmYnvoTAc7KLKIs0CL8QZR+1j+vNSaagts/MKTEhaEY4iokAw/y4c/azoYUwY3eHRfbSZh315vq5Nb+7luBg==