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
- 1d9910e30f78aeee2520cff828ec0ca4f7bd7366fca06e3b1cc9d8f6470c2c80
- request
- 8df04f7294b0676c4b2405d1b2640283c12a8f2f2f5a5ad7fb30f42f440e38e1
- transaction
- 583e83455188935ed9f67ec7c5239abd3054b81f44812f446e80e699ffb371f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31066
the chainentry 31066
- sealed to the entry before
- 4a7c0a8fa0daeb44f25650c2c99fc6668196f35f8171ad681d8e1469e6d8de94
- this leaf
- 819e2ab87f31d1cb0fafbe4d610ef6e0bed19c4f52b1c5faacbf6dc9655b6f8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bZNCEZ4aUJmZ4hN9hqNh1XJbIvLcmvnglBsqvhDUa7Hfsryqsnb43M46WK4eyClOiJJudPgVyH8QHpdSbbESCQ==