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
- 58f0246f71ca19b94db9be6ba6cf421b3666cb4e11c2c68db079e151136cc62e
- request
- ff46272dfa5e712120c1e9b9bc60879f65082438a5f75a348165522e56b1dbe4
- transaction
- f1c9f173f60aa5566d0668cd5f18efed7709def9574a316fca15e538dd530933computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24608
the chainentry 24608
- sealed to the entry before
- 3f62f2ab6b8a3bee9cb4170b67de6ad545d642cd9bb2dd641d9632a10c5bbb8f
- this leaf
- 7fb84a66392bff74f2ea6db1568128cf6adf565358ddbf814b9904bc6d038d0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aB4yzBLMNotMkcn/EEIaVkh9cJKrZoVGgzdgd9xOTcCAa+XSq2JDx5zaTUJjzP5m7pI2nf/+Is1vs0HdfJY/Ag==