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
- 8896601460bc9607d88b392c2571ee434ee87d6b71f3428e145de9db918c9699
- request
- dee7439daea64b12973eada0459ff64059db62d76885f0ec22a1e44bccdaabd3
- transaction
- 533ccb4759f282c20096d09b42bfe632fc93c838c7bfeab7c1431675a697cf15computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28854
the chainentry 28854
- sealed to the entry before
- 559dc670b2bef17f07611648fc08919e2c73343fadf65b9734d377c0bab213a0
- this leaf
- 52726f08122a516898cd526b9e2d27fe4f73edc6bec673f462ea9327c911ab4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xL+Wo8NrQCcb0o8iS5MEGeY9b1B1fqnjSb098ZH1Rpg8dxkeveo8YiciTQaGJqgo03Vt4QYd3bMjNxKYYPkTDQ==