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
- 4affc1f7f670fb20ab601bea0e3166e610a0c143d830b18c59ee74589bdff050
- request
- effc2bd1d3ed3a2838159e37aae3026cf755e6eaf41159001814709d7135e738
- transaction
- 3eba7c3866b2eb47e11c555ae85bdeaef9687e46ea5052e41e95b2e0e75878facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67735
the chainentry 67735
- sealed to the entry before
- d594f23b63427250561b7a8f2cec2bfef506aa64be0fc1a2df9fb0b13cd49109
- this leaf
- 3822208363642502979056e76e111328e542b1d72491a360fe4ce426f669c2d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Wm1PvVCoWqDfo7OOhtY2QgOMcdyNLVlFAA9WGngMkUejozY10ql3po6mQYbVRFYhVnBNnnWvsHnhdmzPQEchDQ==