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
- a13f428da0ebeff146f3021b8052e65ef2eea4c848899f63186b0a927a883bfc
- request
- 3ad3419b6cfa6963460620db0dedbff764fe65ae90545a18664d85740a7617ab
- transaction
- 9101f7208310b9f28f70c5b6836e9ea223f67617594a2f06d8bc8177ffd2714acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11347
the chainentry 11347
- sealed to the entry before
- 9ffe38886db08d34485a629e19fac9f340b19ee4b6d47d9df22865828eaf019a
- this leaf
- d03fad4f71f73af751d241b85dcd46f582d8afa1bb3db1a3352b050eaaac12ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +uAgIINSUzrvkdxigD/z6yd6aF4Z92/qWYkV+xbhm8VudLHAzBeOASi6T0ks5iAee9ydZX1gvNIqwsHyQ2nxDg==