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
- 81ce96374c5c15f30d54534488601d90bcd6fbc919dd35de13b33efaecb9d9ce
- request
- ab4a6b6d4c907c88a768ff3e1dc27f98680b211350309f8415d6fd104e9af483
- transaction
- 0c270c05ec51774a0819f7ea7ce344b97f05eb3ee3c2976edc1e1b9c2a7ecc70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26424
the chainentry 26424
- sealed to the entry before
- 57d4be762e5064991992d2a8ef38e9167eef0fa147416902f54ff0e55bcd2ccc
- this leaf
- b59c7f30cc50e8cc3758294b2c0a07069a5a7866a04eca28c1d00b6c203f1b9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cNghvXTBwygek5XghcDmNjN4F0lsrmhUa5O8VulCY6nMD02Xmld+qZb55TACQOTFDJdHnBJwME9NJ9pS5d2wBQ==