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
- fc50866914a0784f4f688cdf35b41beaa670fb263cab53004f29ffb3befdf243
- request
- a13762f59390de6ce892e94edb9924a2626bbd7b6fed465243a4faade2615052
- transaction
- adfe59cfdff146c5e613dab510ea8608f0705b3bf17191d16f3c49387e203dabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58098
the chainentry 58098
- sealed to the entry before
- 75871d377515fc1a5cff00f39a0e9a374ca73c0b44c74cdac86ee66863cb450f
- this leaf
- 2073887d4dcae51e486d9d30e45b50e1a6d93443847d5d2824d82b8fe25fee26
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fToyWR6JuiIpSwj8NAM0vjqnlHwfZhPb4lqNlRa+vx57rAaMVKt6hbepTU+s3DtKfnPkU7+Ul2o29iWbzh+IAA==