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
- fa40ae68c1ff40ec604280836ce824ecdc80f10663c9fab928af4f579f0c0d6f
- request
- aaaeba5ea823b34c40effd1631f1877d454dfa1401925b5cfed71b31b51230a6
- transaction
- 765c75a56182739a7092ad664c3dc8548be47beeea95661d27ed2aa1fa4477e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23526
the chainentry 23526
- sealed to the entry before
- ade64dc9787939d13b0430e767608dde152884ad953366d386472445868ad694
- this leaf
- 017e9338ad0ce1bd4880031cf89ebc7ba11bbeb685cd4af402b677ffa7b42952
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3hDfXTBfJECgEXXzoaJIsK3ib3c6iaYzY5FkPmJ7x8JY4LSmtouB5EOwQK8HrowWa/wSH6XNbXBgoklX5YGkCg==