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
- 81a7973e74400b97e8961235f340ce375284dd4beb41a2748c53fd8331ecc395
- request
- e93683f0a7591a837d5fb1e2c32d6d74bf561e1a417b380db06863d917e45641
- transaction
- 17deea8ee928d3caece0b8947a2b99ef9f7709f3cbd02045a5587213221fc86ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67489
the chainentry 67489
- sealed to the entry before
- 4d36ddd5c7444e890896158339226ed156fe4253d48a35909ea2aa0e966ce4e9
- this leaf
- 6445d79d65fb0f70cae8f27d50e11914fe8a05de7ca5f21b2debd7465a70fcae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xGYG6BUbh/FN9wLsMaXs751rFQZyE23hDGhyA8X/DnOJJcMRyKaLzWxELplbMaxv4hSnLRxozVVbgxmQFbkFDQ==