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
- 86f7c8ad00af3329f121f134bd423257ee7b02e718e99d7f4265cd90db4a75c7
- request
- 7626ac4ab6d3da97ff4aab5dea857465a88b68479433397546161a8f0e8f2c7c
- transaction
- 11ebda0abfad5d6c97801023d36ceda83d454ab2838cdeca907069aaf5943e0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5750
the chainentry 5750
- sealed to the entry before
- 4a7886132b894bb976d3a2e9a4e0b861f7671b15922106c60269aa8474b56c4f
- this leaf
- 77f1ce5d3d2b36cf01a1ddb4083089cc4569f8fcc2a646156abbf53212a04eed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KpBPhSE3cYYow3j7h1/IGUfKk3z5V7mXEdFtWlhrf+GmAMFaRrHmxerNquQyyl4RT5JTmhi+0m5FN1erlXCxDA==