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
- 858b1b3d8badbadcfe0b052d8bdf24197b517327f7b9e07366c8857027130630
- request
- 1af0fa77f84a70de96e5b077a1f55572c43f925cf8450a8de53615c458e31050
- transaction
- d89a986fbc7aed593874d98f2f10664681500242e6846dcf66df2c2fa4ec53a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41107
the chainentry 41107
- sealed to the entry before
- 257758317975d52a8f3e387d3ba4191aff8c443f1622d15300db64b890c9d6d7
- this leaf
- b3bad0c1036190156b74bdcc5d1de9c3d95efccba0a51c5bdd3558afab9bdd70
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BoHso3y9b8QgbIxHS+QtseFbUaHXIex9caYnYKggl5xht3hLfcwpr9zg3RsOeJG7MsGRn4jqfV86x1W+Jfr4DQ==