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
- 4cf3e459b3ec9b97486eeed4dbe3a902a2beb2e9a63714a0307d249324dcf112
- request
- ea27d11fad1f58f8e136434b2a3d7617cc3b68aa000e15770808d2031d0a20ad
- transaction
- 8f4d198488dfcba3c846b3d78cff3a83b7c39b98d445cc5007a69dc52e917378computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33841
the chainentry 33841
- sealed to the entry before
- e41645a425c4383e25a0007d87bbcc0ff77cd3b4d9f3d3d591d130c175f5cec3
- this leaf
- 2959f73dae3eee5e95431dfec16080731d3242871e2dadf9c37b20e73a578631
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9QJZRJZSJ9DdXjP+rEf6pEAitZ8nMB/GhFk5X5kQMGlAe1vyRJSavtl9Y0KyVBsf41tskPwDLBbgbOigSGYHCA==