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
- 78ba06e39c1f8533f936ff27e4acc5320fb22670e29e7926580c4358aacb34c9
- request
- 2cf72b342c153a27af1eb0b0dc36259d13f57b791eb4364a660be1f82e65377f
- transaction
- 42d6bb3da304f3dc27ff39296e3b99b4c0ed8948fdea66165ec260d5d10611cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49453
the chainentry 49453
- sealed to the entry before
- 51414acf2603404e30002fd1469dedcfe13ec2750d58620f7a71114aab1a424f
- this leaf
- 0a9b7c0657828123f84faed83c24d3c2b0c107d983b647b1ed8d95add6fc020a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U5TtcYEP9OlSu5KI3PtFjqBzVEMlgnsWRBnaPaL5s8lu82eMJti4mBZnshKM+mpOecg7ClOGe8QXcY+u9gpYCQ==