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
- cf77f56831aa965adce07ee7bb7d269720d579360b2f34aba489ab829636276b
- request
- 8171fd593b6edd5647f6c11640303232403cac313b33e9a12899c0e8429d050a
- transaction
- e1d49344d9c1cf6f09120ae35af74315d641520baab499ecd7544bbae501a488computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44153
the chainentry 44153
- sealed to the entry before
- 8e0e78910346403a47a4e419f6ebeb26c297b532d509eb8499e27a202008d04a
- this leaf
- 1627399045e98568148e3d44f0a0fc91c6cb21d7f7d0518b52c21b6a8b4c09b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wTeVhJWlpUId09/+7cKliBrsKqSkAYOErGDM5O9L8eYr4NJb6xYTmbJaBjVFcBX12TuguAsqrdUfHBQxK1r2Ag==