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
- 6bc71fb6facbed51f3588e107d2e8dcceec9a6eac0ba1542f4d63834f6b16314
- request
- d3e51f95a6b8379d24e148a142592fb77c218042b08a5801e56ddf8574217e95
- transaction
- 22f53dec25cb9e5118b4c9e1f54b1db86c6b0dcfa2497e9c1271bcb287c2074fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26029
the chainentry 26029
- sealed to the entry before
- 82452eddd00d1df4d3bd3f9e8b21bf15ed45702147ba36b198f9045afc66ccb9
- this leaf
- 6d092b73608dbb79fa5fb964a314270eaed3e26c109719c8b1a51a392ba74b56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hRmFHd5omqXeMtXivM/hUWVcxMnL+6c9CLPH52wJq9mAGceOIuQMt9H9FfeQ8/qrK/ZmELlQZzkTzdDlr5AqDw==