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
- 30873484f4efce86fb5088a759444074884e27f5a6770774ef6a643f37cc0376
- request
- 5e44872eb7705e0d06333d1cf1120debfd343ec85de716249cf41383f81ddb15
- transaction
- 44bb7e5d6387a8a90e64c7ca4a1351afa0ef5dc6e4795981fa22c873cef9412ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32918
the chainentry 32918
- sealed to the entry before
- 07fcd9af95c96b9e540d900a57124628cceb8a4aa7e37e0ab99ac456782052f7
- this leaf
- f87ccea9912e3cff6d3159ff79e4d20390a5753900ec8ab32eafc01f296d1716
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UAPa316L7mzwFCEZpIkv9jJUdcN3mwDRB8RGMtUfzmZAMdf7S+FUiXJ9GqqZH4fUMn9j7q9CmK4hjUlaWTMyDg==