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
- 602c1ce60242cbf9539d60272b6aabac90f3dd6d3e56fbc162ad7e48d2208e5a
- request
- 33fbb77881d46d0820d1e68486c24467ad27ef7bc6061485237fbbae0eebb950
- transaction
- 01f44bb974b200116a2155b8be4e44f1e39a4a998e18e3b2859842d2dd400926computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29653
the chainentry 29653
- sealed to the entry before
- 9e71f40defd514684cd86c10e3c61432984c57bf1ce61b574161ece35807e402
- this leaf
- b7e2f64598774918b3c94d1387beb9d7735aa21d1a164b1ca653d107de7b2f3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 95k6xAD7U7ZpNWdZqETjwAd/0JRSSwPoWqKYng1WQS//CWxY9m7VtJO6fZoa3byg3lxFXgq7SiBmoDqdR91RCg==