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
- 26c659ae96a9ded70f1c2cb484a2577a57148292ad3f2019c700c503e0e400d6
- request
- 4995754b6d874f34082f14db1f7f96bc554f12ad7dc0a362dd287999f38c588a
- transaction
- a58de6d795c07d57a85c18fcabccb837b47fc267d5cc6a70302fe344540a95dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70572
the chainentry 70572
- sealed to the entry before
- c68aaf951f78d42450f23bac3e7c53398858ce4da77f71649a3eebec44ac59b6
- this leaf
- fec89b6bc59deb53e71c4f438ef02aba2e3613d3ab4f92fe39e5a8ce1e45cfe1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NhbDHG0xkunt+P9BH0RUpHehkkQgRpkQQFwbCTR4y2gdLzdE4nlYjTZ/1Sw8wvNwQHD/UYN7A1xt+VrhBT3EAQ==