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
- d156edb33c749cd6bee31e966366d43c154ef9597ef9e59f29d62fc1cfd2ae69
- request
- bc3397639891381dcf67d062ff007b41942ecb58cbf63ea37bbfa3d4600730c5
- transaction
- e3ec0025a69da3e518794697c09c4f80bcd856e3261089208e6f1f4923521907computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43164
the chainentry 43164
- sealed to the entry before
- bc0bb759ecdb405da6172a333bf213f8a847ce937b165c4e458baf188d943069
- this leaf
- cb2f5a241cd6082d6cbe22aa9a722f8e8a9f9580079e4f0da26a95906612f596
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9M6EnKQrWCijBxaXKlBU+a4yVii/em0h0YIM0H7+7q2m6QUqD34TYd73Wg82eiHhP3JyVjb4kuUQTmEyrP2SAg==