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
- 8b6cc018137054c359f6dc203f548f6259a3d5fe23798bccafe7b821d9c68534
- request
- 8559685e729154e54c633adc40a4de4c07be576fcd82dd11db197a1e9522ff80
- transaction
- 4f34682c3861bdb0c4077db29550dedd8f01e765fe65dcc7778786a163c2a268computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77337
the chainentry 77337
- sealed to the entry before
- 0059e721c13ff0ffb8058471f9a2dc0a6c0073e376d6d7ce8541748222e61488
- this leaf
- 2d63e46687e025224e4e2036ace189756db5f190a21b84d88ca004304a536235
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dvret+DXjVhgvrTG/s6YETrlwvEJp6jR3V8BgBcFbyVXZhGl1R7e0gtRaujkrAgzy1wqj66D01A6l73YcHWEAQ==