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
- b0cd8e1f8a39d96297088a108284feff807e6863013832cc3027a95f695bd316
- request
- fe834622c34db8446e46de8919de6f301ac5ac2ff93c432617cb47fe690f1e88
- transaction
- ed2d5ca0cf88d25e29cbc97a0e52c43c241d9361188697b0a0980176314ff4fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26309
the chainentry 26309
- sealed to the entry before
- 186d3f9e520816fd3f597ac8a972579265fbe0e85019ce7dc2515c80c57c7783
- this leaf
- f1f466c9ea1b10b244906748ce9d402bce7f3a313d049c1224b3c90347767a8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lPDf919EKx6eCIq+kVdh4xG+r7CKQqzxEW9wez9d/ssD71ljZavSYQ0enecULEp4YN30KxmVjBauNCxVUAsrBg==