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
- 6b75b128f40a654fbc60c4312054efa1f4111a416db2b29e90c81aadbeead616
- request
- 0f15266bfcca69a37e244f51240eb4b210a9bd1332a46929857a959f8a8268c3
- transaction
- ac56eadaf342fac1270f5594685fe898156a7f16564dfa056e67fbf7e80ecbdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63448
the chainentry 63448
- sealed to the entry before
- d1f4752e83ba6ad8752aaa1a8ccaaa787e1ebbde3b6d4c8567d30847e3aaaa4f
- this leaf
- 01a7cd3e3b13ac79d554090fb49749c7b8a0023ddc0584a336dab1a6c71c2972
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S2PwUUXYeJwkt3LQJjnKVL+zzc5kaW/o9JPXwqvZKVbPN/pqt8BmMEOrOlP7wtT7hUC4ytl1wE3g/cFTn0ooBA==