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
- 79bf91a22f7b480007a632a7de203de0a89212ddb93493a76164be6443e1efdb
- request
- d86abbc6bae4af60067a29509813286c5b46bb7dce3051c67d98e77e8a9a4d4c
- transaction
- a9e824f2ee3429d4c29483ea9947e0f5e59d5dd17f79c709c69683a969fa82dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29061
the chainentry 29061
- sealed to the entry before
- 85c7ea3ffd13404456c380bbb4dd73316b77d8f1de4a3249dad5d26c8319d23e
- this leaf
- 581c00de146bdd1a1a763dbe003f46cf0b53391971802ffc1efcc3b6741fdf49
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0n53KnbN1ZSEmvjnWHcoj8UZ7sNunJm4zow8fI65YGzO6Nvn4xtAN/tsvsEivwHMPLSIbKxwtRr4exHrywWgAg==