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
- daef2e574161e526790a245981dd2e1c8136385dc88fa6ac0e0c101a97c32e53
- request
- 1519f28fe812281cc3d2ed9e66ab8ebc0564349b5fb481eacbc19d331bf3dfb2
- transaction
- 26a3ed1b37b457f965e68313991fcd9bcbde4edae6807d01cc9a380c065d967ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28044
the chainentry 28044
- sealed to the entry before
- 7886f7ed714c792e84576f35d04b655d6c582e5b84bcf7e753e66439dd4d4c78
- this leaf
- c975e44f8a0879759ddd6e3f9a14713d97e08c057dcdd396b32c9cd6521e510a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fAIEciLUTwdYxxOIXykr3NnEwBL7rnpGwlbxC8ivlT7b34n4GH1LzoNDbwCnj54Dp0aDSVARyvnVEScbJeVECQ==