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
- 59cd6d884fa0baccbcbb91f2c9ea44eb6a23cc733c3ad910b02d2b8c31d026f3
- request
- 967ff9f3f73f1b99958206c37fb80feaf3256bc0f1eb097ccd171432c49cc1ff
- transaction
- 107f51b8bf0d863de75f3e4277cf0683893cfb12e87b6aafdf63d68d29313414computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66068
the chainentry 66068
- sealed to the entry before
- 6f0ef1080de2d91f99dabe731191ee807b9cb694d7bb11619736758fa79677ce
- this leaf
- 9574682b76cff5dc6b3b4be9a93024ef1f869587517f332ca7778c866a705e97
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S7yfhpwX+qFfveO5BdnZmI9AT+wSRkzxRWcaABJl7TCpk/FkjnxhhhQ0KeeAtVuf6ItOr1ukkWpbvYzu0wtTBQ==