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
- 7cae5514eb9978ee933ccbbfb5bc0365da3a39d3bf60ce9cfb5755485fe29314
- request
- 113b6bfaeb47fc59400597f396bfe1857c4da9bf590e510e26149d1240d4fa45
- transaction
- 016c599330b22d0a4ee60f814864ec730927b0963bba2d46c517628970fddc1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26495
the chainentry 26495
- sealed to the entry before
- bb472ab23b469b51c1e3be50419eb78aaceb1bcd4792710db073e22db7d68d04
- this leaf
- b0aa33a2f3a0286634468983e913ffdd04e963c0d726b0e25af8a1d18502cdc8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oRRZsbBiEkGcv0JqWWpr5tAzM0yoprqBVwwWO3MMvfw8HV87LN/lFr9CX17FAT6zAMdw6SblsccFJWwlrrCGAg==