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
- 19a9e6cf933e3852daddc9141580c8cc2c0e13b03f4878e20469e15490ec3ba1
- request
- b66aec01115547494396435c571618adc40c14db364420d45e40b6ff9586a872
- transaction
- 53d3dade65c28d9f50da36e364ed99c5c0e054205bbd7b2ac229f35d13f05f6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7886
the chainentry 7886
- sealed to the entry before
- c7cb651daec98536e19cf84215bca477d92655616eec1b989c6169559df206e7
- this leaf
- 029555893d7e8302a6663b012f45ecf053c5c1ffd1cbedfd16ad415b69186fd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +f3N0KZ5002lmyY8ScLHfAsDtbMKiy23KdSwgvaTNbCt26lgJg0WzTHz9RG28RUub2UTIqm5fcxpV9exMm/QDA==