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
- 689932b564f9db15ac9bf24076b87d5ac445065ee835e1d72f6a35999432c11c
- request
- 9b49c4f727b773ce8fd48e7eeac7374880564c97d2b8eb54a539b98f306f34db
- transaction
- d7221167cbd056f891323e92b4b9153dac8acdd4fd5ae675a89311e40f2e615ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 206
the chainentry 206
- sealed to the entry before
- 31c48a54cacd7299462eef68bfdd05594a402deabaee2b12bd4c2d70f2ae6cbf
- this leaf
- f7caa5a4d94968bbdcdb39b2843b18f2d93edbdbcd436edc7749411e7d410914
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RqO7YnzM5B9gY4ipEN0MBTUrFPWYjOHiluGTFqBzz/4LlwRZM7VeAk4eZ/Xaf9jQN1kNraI58TTkvyahoaU7Bg==