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
- e910780d5a661fab32bc7d1dbe539ae64de49db4993b1e35ac03528f8f5c71ab
- request
- f005c4a03fdee1190d8b835ca7323945548e175740e9ae245e3b63c008403e4d
- transaction
- 5cc07f13c9a081d78cdcc0a801f798dbf6b7cbc862777f635efbe3618e18250dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71112
the chainentry 71112
- sealed to the entry before
- 4d94c4b34772eab53d3677b5c1581c3df5938e2d1d85ff2381ccb6cbc1417f3a
- this leaf
- 8f25316a4251ee92492b02fce4c83610e2d622e917abe1bacc7d76b67b04171e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ynyyS+Xjnsa/H0XNdgS7fD+DJd0J/DqHdzgOBUkvXkxQKARWrMWhwKzpF6oNUYC5gsJDMeSzWW4OpkdyGD4EAw==