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
- 6dc229d47da102fdb4e2204c82285ee0fa97e15e3b680f586e2738bfed5776f7
- request
- ea030d69b515f31d6caa2763a2b0578187bb5896f3b8592c54fff2cf33f3cd89
- transaction
- b6383d05ac5b2bea99b9ade960699cb8f15bd87ae5d7f2ee2e33afa836dc0365computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8018
the chainentry 8018
- sealed to the entry before
- 6be1960f4b4f59ee4020769b1718f9951772af86b85309a70e84facbf3cc20f3
- this leaf
- 86358a315a16f4e6529bdca8c1bc743dec4ef136908649a96565a7b979c558ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8NA3Y2opPZ3I494NHLjLJSVDpvIw+rfnf0gulTS7UkipnI8UP8euGxNfNgjie425LM8dOI9mICCksgA49YDqCg==