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
- deb947ef29e260cc8fb7b8dd4694d170f156bdc37e6a0cfcc1dad36ab3f69f97
- request
- d7e489013062f53ae0460cd762077bb238c1306dfbc8417201b794350ae120f6
- transaction
- d6cfb092aa525dc8a543f4caebd6eb453e511c2c25bdfd50ebfef998101b6150computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73157
the chainentry 73157
- sealed to the entry before
- b63610ba0bebe9b336bd353b6d62cd5c8d13d462c5cf4c4c6529763fa13b4ff5
- this leaf
- 3a8e5c4c68cfb253b208d40bebc1e464d4d98e433c6d23f1a65901ddf2a76ddf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mU5FsK9blff02+XuIc6A2AN5nQw8+EedIa08W3wUBGtVuLl1RkiBVPkdXgUnGAWrBxlQXqkANxW5NJ3/rFqiBg==