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
- 1a6ffc0c609044c753cf19ca8ee7fa26e0ebecac4615b8f55f5c0fea7e454d8e
- request
- 8c97a277b52436aae83e5bb1a0536ef32041ac7b310f4c825ee9a2d7904b2b18
- transaction
- 70de16defafa965af830fa19c56ae5d1efbd63ee1c82c73e7dbf1d17a9c26663computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10756
the chainentry 10756
- sealed to the entry before
- 8485b9e7b9705860f972ffe22496ffa99ee17de941a69b7f24e7b3393e1b905e
- this leaf
- b04efa7ae425d69c238394f15ec69d0c5275fa0bc86d2ecce16312e0b60c0c48
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- brfe1WL6cpleyMwYPVltBp2ttLDST4yJVWf1NWy1pmaoYlTh3JHCTNyplElas7bUF23YS0zxbTz4j3mZ7ym/CA==