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
- c35d9a3bd9e48da36e195a1c982a58c44428e6aea30fe45adefe55d77ad560a0
- request
- 97e4c570690010d8d08d2461e641d30de7fa4e9525a2d5f510b6704212fb8c71
- transaction
- f61f5b8e797271e901411cf4e681185723d099238cbc4f18a82be0c11a1b93e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27874
the chainentry 27874
- sealed to the entry before
- 3081e458918240381b86e82803d3d7879b0b16b6cbce6a9df2f02d7202e7c0d9
- this leaf
- c2e0fab9a9149815e0a3e754b318a3e464ba1474fc2c5836c172393e542279fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KaPLxXJKalmxZId2cqxlYUuicmnAwHu7oV6KuGd66bi5Kmkdf3yYwM1ixJillksxICVcDXCmGo5DKNvuSJm0Bg==