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
- c2c7e98fc07942f4a5bba7d81d29108642bcc56edf15068301b2f773c26b8b29
- request
- 94eeb93740c5910b4435e38a739d9bd328e89e4330d778f90b71da22d0ac1e86
- transaction
- da70dc1c2e07b55b2d6cd0278bc1b692b31872017764ff4a3b11fe7ed1fe8b0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39523
the chainentry 39523
- sealed to the entry before
- ecc491113be5eae662a52943d0028d1f029b57973ae9480286e508d5bfeff901
- this leaf
- a7cb4d0d9442b361a57f0cd4f1922fbe70db5a72694af9234a524fa2deaa5e19
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wwGmOAKYAuuo/Gss3E76ElB7OLTP31jQvY9IqQAZLfoMjHNPYN7lHInOZ76Yh2KI6Q9foy1xPYJJcB5xQ4ZwAA==