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
- 3d3f7ac6848f0601e2e35665a805aedd23ea7d755fc103e69af5412c7670f8cf
- request
- 1c5be54f6693629a50e678b6ac6f32532513473e9db1c232c230ff3e40b8737e
- transaction
- 541edd609c101d8fd4da22343ff21247c9e95934793f6e9e198174fe661b2baccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67417
the chainentry 67417
- sealed to the entry before
- b665e126f12b220d1f32ab733795efc2db50a9d23bee403128c7bf6d036c1f5f
- this leaf
- 82249e9948e8246f0002e558fe79e3d45067e718589dfb42c625783f206b6aad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /e9Q9Cj+wByJ+FwCc20wjh/VMxJJjrX7ZLHGlwseVexy6NPsgPBKsdQhhrgkBvg9lv4ZKNAjIBF6h+mzT4g6AQ==