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
- 4c4cd72568d9017ca80a30d1af08f48419b8679693626d7b448939414fb807ea
- request
- abd459b92958341511b8e6201bea060c909a0d79461c0462d8e52a533cd491ff
- transaction
- 5aaf33255e1702c31a64ac9b59b6040de23c5ff584ca33c2977e5296b2341e4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66213
the chainentry 66213
- sealed to the entry before
- 017e389dae494c77c6f433f3b4ca07cdba6af155a97a5aa7f99b120c5637ff40
- this leaf
- 1133f3d9de348e24dc913adef1571fab3b46f86fd72f12f7fd215cf7efb9665c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WPKIEklcgLCanUWYc/AabG2gv79VbQ5a8npg40ITvRvbjABMlsrk5V2LCASkI44hJrHfzBsB5K2JHOK5lpCAAg==