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
- f43072def0d585e1cfb4b7399375bbb9f23fe6ca76684243d7ea9148eac2d29f
- request
- 7529444fa4834f994b1c4f32f36969430b574c7efbe17879aa61179f715c62ba
- transaction
- 20d5609fffbcaea4ab8a743864bf124b6fd3cf24816584df6bd8094f87564d5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62665
the chainentry 62665
- sealed to the entry before
- 5181ff61f84c381c66f9adcccb8456c43636fc1a9672882bef3292404ed9f76e
- this leaf
- 6d3e4aceb278a3acd491d2d72a05fd83c43a76e1f3923b2be37e8bf0199a3c5a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VY3kkPlyh4JelwxFJdq5Jog59lexv9hz/p5wr5nvutzyR1UJ/tmgRpPvLNbOW2Q050f5FplmEEh3MjMub2b8Cg==