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
- 1075ef5845701ea429c19ae09da18f7bc4f238a5712508d9eb3a5604ce199aec
- request
- c29a2ba98172fba9f5c144025c151eac2226b5dd37ae3aa7141ce1575cf154a5
- transaction
- f85a317392eab5f22bc67ccc2301c862b5e813a46f1eade777eefa2f7b08ec7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35595
the chainentry 35595
- sealed to the entry before
- f32f3473b6658441fbd6bad1aa9d026d411cab6c96530011abdb9ed28ea42d28
- this leaf
- 4ee43b95077c3303f517c33078e90d6503f7970194013f725c4454561211d541
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QcQhZU36sQ4zoIkLoWkLLQ8CgAaFNt5YaTF/ZlQSW0FsRihGRwzoddIudkEdlsOyXckkauc+1oi59qdXTwIeDw==