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
- 7c6b775b2b31b21ee00e80596f777b76dbab338c1b1ae1368026a8b8079943cf
- request
- de019ff644df9d04fa25840937f2b1c297482c41ce62ff787bca60d281358a78
- transaction
- 92a6b2027414f74e930d2f15672e3a04546710e7b636358dbceb9283d22eebaccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 963
the chainentry 963
- sealed to the entry before
- 48d28eeb5093d4b3985d626b18ef84df7cf952287a38c4fa0205a8093e17feb1
- this leaf
- ce167d2ef29938054a35a988e120449c8db8a2df7d91c4367e0714301042866d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zBw1AKWvPm4BY/PUtHl9jkQizHBUrcZlFp7mANtX/u3Nc5AddZmVIJfR+l70WrmgeNMN/2LwK2a85eQqMAqPCg==