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
- 160dc851302337ff5c850a504adade147b4242e82181fbf0a6144bb9e11b40fc
- request
- ee83a9b0cd272c59132898f346db7920cb4a9a4b61d47d51adf253f5e65d69f9
- transaction
- 9b0fbf1d66124ab7b51d090b871e19597b2ac839d122f44964565832f168673ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63280
the chainentry 63280
- sealed to the entry before
- 97d93991ce2e470920c4f806dd52e7e3696e56b3fc3627c30215efceaeaf288e
- this leaf
- 5cc99a1207a8f3e602ac101c5b9282771f7ce2aeef22ae8ca5c926614a553a80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R1MVzXd5LV0SnWUtu8BE7K1vdBPeIaP92sbSkJ/eXlxCX68ZKo/wpLlzyBHzVExmxaDTvegVCOAO9/3Gn4zCDQ==