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
- 6b742c2132f9ba5a50cc6d0d19bffc6a40cecf3547ff8190a0d3a182c635487f
- request
- 80de4c080d97eb9e90632a77f39eccfa52af81fa35351d1af15a69f8b2068969
- transaction
- ee14cc0078a9c4c333e87bea998ee3aa901a889450371b35c82d8ffe2c4ba710computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63506
the chainentry 63506
- sealed to the entry before
- 3e7fee648118547c5043530a73e8e497b29f5797ef9a8bf67e3f1de0beb980ed
- this leaf
- ea9d3d88d995c81e153667137593f8bc0a32ba5b4df9596ac564529c1a709da9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fLtdMMwMk0VGnZcfl9IqJDIac/Mbe1R/jWPeZUJTKQ1WvMZ020Xgaa0LzBeiDkMDXR+GiqZsyNUYKMv09ErnDw==