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
- 1dc868a9bd21862de8bb4f228d03487d18fc6ff5d32b1c6d62a7c4576a8d7bba
- request
- 2e067961ebbd1857f6224d6f15cc527bb38ab618f1dd73064d1977d0e8e40768
- transaction
- a2690101aaa2062cf58a5277817d0e66dfdfa6070288dac9d7c405337b7c2ba2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17950
the chainentry 17950
- sealed to the entry before
- e4875637483f936156ddee49881ed1eac8d706a0466e53c58d40a8d77f00d5f6
- this leaf
- a4a348048aa38a0007455608de29fbb3cec9e4a45690ce8274e38aa4dfbfbdef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mKymyjlskrj7oqyeo95mvQQJdMSehaNsuBYnDo8x66KadhuL7JJLw9bEYLLjO8JhQKwAJWWBSq6GHvzpOM3KDw==