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
- b79f28763c71c441f7e88514372643131004b4d26f852173b3d7ba67612db2f1
- request
- 9f67fff2297d7842e94205f3e8432c7109487a5111ee945ecd15eacd822f923b
- transaction
- 211fc49ca1e2582a044f3c3ef198ebeabf7b65c91beb42d64aad93a2cffea3aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61580
the chainentry 61580
- sealed to the entry before
- 1dda496ed92d7bd8546e59adda59f000e543810db65483d43e1a571cec457ab4
- this leaf
- f27a47f46969e011b24c426eb8452244a17b81100ddb42c3d577efb9e5a4fab6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ztFFDubA9S3pmeaQ4rPxpUm4H7gBjCHjeJaZ0pSc2ngk9m4UQn7IT72HH8Syy/oSOC85epMmf9h18oOAH1TeAA==