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
- 2f6479e965703b1237b43799d4834f5bbb9a298f4da0f9b354aefb37bce12cd0
- request
- d5d65df179e79efae4431985233078d02941b175f4aecc9d4b97303eccfcf9f9
- transaction
- de897ef470a37d606b7b3bfcbc2fe675512d91924e9d57abb2049d3556f56756computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22124
the chainentry 22124
- sealed to the entry before
- 5258da1e564842d1ebf2c57f8c19eec48acee7ae1435298bc8e7f2419806e071
- this leaf
- f6884ec722cbf334a2defa6321157332e8e1b164a3af8ad6a4cbac804c2ee65f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dwpjd7i4CH1ztNWl3IDH7iV/sfmip6AcFOVf1IyldYwndHPhB2pTFClC4hyeRzMYFwiLoHsG6dPZ9Ua+kP1ADQ==