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
- 17a0292f547a021326192bd6d305a2006808c596cd37b8adb0260932904ab71a
- request
- 60db83b8669938c4624b648a471237b41c7f8685bd4800ee46f3333deca9567d
- transaction
- 3416410150ad5add631f006f70972027186539d71b28a44f4bb77691e930e76ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44462
the chainentry 44462
- sealed to the entry before
- 65464d78e9b22cfe40a52b9ae9894116add608b3b6d2f0a17c575b07b3ff6428
- this leaf
- 900b211d276a68ebad8a7846f038e8395abe6d51270206c2c84e1155e4cdb51c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tD9wWRNjGwSSd34jv1QSGHtK7M+v/e0w88gq7oQBROzixYwK6pkN2m4eXlkmtvH+llo/eCihEewJ1VrHwEy7Aw==