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
- b4ea94cdba16fcf7b56b17849e4c79ff6964e20ea3d4f36b4e1394d3219b1b61
- request
- 2c32a544210b1d6566ae075507f28c675c88c5a28b84c0b7d532f660bc527ae0
- transaction
- 6b97ef4895f35ea266e63def7358a1867e3885cb74cf175bf42cb2c68d022f89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30762
the chainentry 30762
- sealed to the entry before
- e1c803eff9688d6e89312943798f7cdc0eea83fbd96eb625d747373964e2a571
- this leaf
- aea7d176ba571aa0aa55e9b6a0203f28b0cbafc2b3a729202f1245f2c6939261
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JKsTn7mituMqhiDfSSCno9FszxNMq4Md2dNd5k3sWwD0ftb5cvYd/uiyO7NCWiwvJi+dONTF3JM9K1yyHKiQCQ==