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
- c5c7824a60c5e3b5def09616aa0cad944ca383aacfad05fc81bcb7f8fe44b73a
- request
- 3ec9d22b516f6ac09e53dd61a95095ba0257848a204152d05aa560e3d1627f33
- transaction
- 35eb386eb2d9f5f99951607a0cb908fd4eaa2f1393c856e016dcae6f1c78a193computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 866
the chainentry 866
- sealed to the entry before
- 860ec788f08506f4d95c1e33eef13f711bb77ed5fdd577487c2cfbfe33475ea4
- this leaf
- 419918063051a4fd99982e002075a829c2b8e5a7289e81cdb33dc2e6908e813e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LpBDJPvOrnkdYrp3TEeNSZb0SP/BJGyVQwrLDOIoMMUjS3ypylcu8LrWnBCavyrtKrYEr2oJkyHd6TuwSlQYDg==