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
- 5c7e810e03e5e57b43ab6bfaf277402ff761bdbe4dae3bca888645483159afc7
- request
- e4c9538bb3f1050066f9897006a261ffd71163866a936152a9e2b9367d559259
- transaction
- f8334b11101cfcf896adf2ee0ae514add6ae2c8524bcfce695494b530531f465computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56044
the chainentry 56044
- sealed to the entry before
- 93b2a13dd6a432550a8c0cefdc7606c441f7971fc0d95b904872a783ad5c9944
- this leaf
- bb20b6316c479c8977db7b99c366318d1731197a93eddf6e6c151b431fc5afa5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BHnb+zdkPelKdUHbnk9U4csWTmpFZ8g21BVxJGpAnIiHH+XFfBFApfAYSB40MpThgwlYbYfDMBr/Ij/8ZlQSDw==