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
- 4389f848ccfa8c823946f805b65b9a2e759b9184ea49eda082e460bfe20b67bc
- request
- 91de427fc3f92a35b61ffaa8ad76e6a15dc506275f137f1a3098a435c114bb8c
- transaction
- f74ba6f0a26fc1605043c9d152ef39171ce82e60516331fd17130c7ff6269b48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16274
the chainentry 16274
- sealed to the entry before
- 372c7805b58a24a05f6cd943f9e055b4536af79432a01389a57db666041ecc47
- this leaf
- ff93797c3c4601f182452d06f9eb57b963fc1845ecf45a9edff6ec423a234b9b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ENfUSkjTmVMmoEL+CshK8P/LBSCdBnZDRF1roHZOk7yBqHCC5HrGuxuqcor44peCRPJ3D/dmVO3sp6McsRdvDA==