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
- 856d423055c9e499013901c40738993a9c291d28bb524109550947f75568bc43
- request
- e54deb9275ca3495fac5b549405ab78bf1fbc8922ee7ef00d3a2ccb56adae842
- transaction
- a6a11d28160e0e12ad02853aa45f26cc99674489fbe0d7e85fe788f30a610a85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73412
the chainentry 73412
- sealed to the entry before
- 21c91fb867f21b7281e698420f0627f8f034836d65e316bac950f5843e54aab3
- this leaf
- 65398e04b417c926f9480ef1d9f604454aa802f6df7c104b163e8a0fd95bb141
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- caA1r49Q/5rwjEGuxtTDGey9xqE5nPdiUkTKovDRJXiWd7gb+Uiaa2wwVJ9DNL9d+Xw8SSmwuQV/tijQ6NGzAw==