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
- b0786db5f6cae94352aad119dcc6dfe2e483e001ab444533cb84a32667d64a95
- request
- 9f2b2bf7ac9436984a7589e710bcbcbd31db0406626bea9f13048c7c6ec3dc71
- transaction
- c740e608322925414467a595946881d667616c1894024fc1df4055476904b127computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68338
the chainentry 68338
- sealed to the entry before
- 1f7326665b67ee53ef0b490961b59a6e85ab1e43dadd96fb3e04028faf500ecf
- this leaf
- f8ca2fbc6b55684845efd7b93b96a2dc67d7b8599fc210a64f91b07b4984831a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1XhxkFl0nJ/Zt3QbFx0q0Cp5jCWjS3MPQyp/szVYCBCIYE3a6jwJa4hagK361ki/lzZVk90og+KKL91oobqgDw==