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
- 516f0de74ae0ced1e9912a9727438d59a909f514d392e29f0a642a740122aba4
- request
- 17bd15f7e03300cf0036b8c9cb27a980ecdf8f9c039877e252a133b613cf2dfe
- transaction
- 18b7f9fea2ea003ea0ebaed2bf9c95a8c5a7957682902c78c629ff5c52b6cab7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27839
the chainentry 27839
- sealed to the entry before
- 10836b4bb8d29ffd287f558e2365d5357d738154f9412742cc01df05d9003c2b
- this leaf
- 80cf7b4d3378434e4ce1ff903bc811ee29a134ce81f2077a82cde5831ee17341
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4EVhqNjiFxRmsY70EHkhmEWPiV29f1Gjl9vK3UP/UMyUCbZevzAd5f8NL026WhgfKxPqIyq/8IRCyo4Tk57xAA==