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
- 42603f5853d4ea9d0a4dc1fd3325faaa73240af5301007094d4f0dd9bfd6932c
- request
- 37450e17cb67283b75c482896ff2f3032d1ceb135554e25843731cb780c61a88
- transaction
- 05de8fb4a693d882dd9227d687672a519092b477ab5536ea487a129ce1d7dcf6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22705
the chainentry 22705
- sealed to the entry before
- 239d4a1d5607ae9b214123ae2686a8521903632b81db2141ee60234497ff8d48
- this leaf
- 0d6055c23df6bd3ef223d80817909d6a166a99b7e0b79ba30a5efd14c8e84e90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 78mttZY8coCzTGVt38IOD9vHY6mtf25zyYE9ssVguIiG9kn1rnEEInRQMBX4yTUxJ5NGwfsdIP+ouu94LU5KBw==