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
- 5eefed0e2a942137e49f3ec5bcb23eb66c80b5a13f7f89282b9211b13ee606b0
- request
- 402777f85b8b2f51050751a2a95aa7317661d79f6aae4081ee61e4291df68366
- transaction
- 050e404bc985c89d20a0268b5ac43c5f444e000619560f67466671811348df30computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71822
the chainentry 71822
- sealed to the entry before
- 620482d78023bec402ade344e8c414f97e247bb63f5170156da936ea13bee45a
- this leaf
- bfa3b4cdf1d2181b906f3acf2e8a4f930759528f877379d1e6cf416028bcd7c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AFweFXq2H1nbeusrbMsIrSBRjaIsSheJYDjmhI9/I/BVkYwdCs9sdK38VM8DuM+ciGtGTkgntyDhKcz7fOkdCw==