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
- c155aa5761b73c2872a9a91378dc21ebab1fafda632a430bf15198abdcd6f2c8
- request
- 145d0d28c09ee996ca060a081697445953cb1b6de91618c3c511f3740042d5f0
- transaction
- 4938bb9a484fb3de18be796ba05c41f6f7759509e00a35bb7cd9b456c78b18efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48017
the chainentry 48017
- sealed to the entry before
- c988c9ec244e21f45e8bfd5a6740ba214fee063edf1b847c442f233c636d9e8c
- this leaf
- 2e08ef7dfd87fc248c24af4cf0de5f472d0e965949f2cf163206b2881b850bd7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 50s6RMRhW0SNxx1a5N1/Izv5dKq/MQzh05MIsXXgcgi0JKJde5AnNP0iY6pcARuieyGSdWdNvKx4r3sA31AmAg==