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
- 0e1ab3ceeae590b3fae32c793ecd93a5d5dcaf2de69eb52d0117ef41cd548ae6
- request
- 27d773ac59e61e59f8988421d45a3cad140dc4d966eb720981c71feb305bd86d
- transaction
- eaff6146852a63b3a1cfa6d86096b3c588f909e3f953a8fa6885d979c88aeac7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65629
the chainentry 65629
- sealed to the entry before
- 73001316262e95b308d338547f0b491a6e6272c42a77e71667256e96872ea03f
- this leaf
- ebccae55b2d3d694960ec905d9516252a8ec230c5cfcaad2da63fb7b653b7a29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YDhYrXiJsl/4vrX11qHcR3GUWnwzn6FuQWjA7TErk6LhfdIA2lMzCxWK3BcAU464KBw58Tjyh0p4aGS99Wi0Bw==