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
- bc99fe2b4caaf0da42be001e400406f9ee9f58f7163c2077e7622383960713d5
- request
- e91c6ae95aca2ca09814ded784005c759613c21ae5cc82d882edf4cde648f6e2
- transaction
- 94a5b352bee9cb6f597690c5c5b3650ad99da04a58c23f4115e86aede901c3d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42468
the chainentry 42468
- sealed to the entry before
- 7f727eeba1e77e159624777117c450c2ac335e628cddd75a8dc9d5e00e6f6491
- this leaf
- bb28c61f0d449805766a0e00aa70926c6af033460302e3685a5d0e0b8f277dd3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Td4lzd3AUkrbC26f0I/utOdb+Yhn51HvTUYnoBeHUfr95a9IBKWPDgKxKQcNPNSL3Rsoqfn6D7RMphpz7AMfBg==