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
- 2691b1bba9860163a16e992ab257cfc2c840d3bdba88639b9337cfe9661bc467
- request
- 6e687fda32a1105e0ee1b31f300a9a2924280876eabad4b33cc0cde2dcdc0648
- transaction
- e7f9f279c9a5208222cd9c9a941b867bccc60cf7cd567a9d6cdcb611ec7b21d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16269
the chainentry 16269
- sealed to the entry before
- 7c7003b29dfd9904462fa3791befd1d0a146f20d7db5494a0a6a341f17f18502
- this leaf
- 1002e3c6db0837a31991fa9cf8cbb97752f92825f11a022e25633084bdb9cbd2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Vr3glrBYbBUwnZ/sfPyTQGeaPz541HhVU81HINpe4u6MASWXdOuKdSxTTYRhB77POzn7ziW2gjzak5vceM+Aw==