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
- bbaf3777da010b8c026339248b64d2c55823eec5d3e36528e80e25bae72ad841
- request
- c4e835b07f694496697fda9616ff54f0039abd9c24b8d79892fd14d38742aaba
- transaction
- c819e70bb9f1ac668d9ad729b6d4b915ae99cf33f6efcd54c79b4f8f7cfd069ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9063
the chainentry 9063
- sealed to the entry before
- c4ff552308a0b8dd3f9a74cf8890331fb91c2950f50377281493f97986836b38
- this leaf
- 36490a54aaa54b084f4c0d26ca8a662b18946101205a91f1fbd037ebd6b14449
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qyq50YJgumHovrtz342XDqj7p6kyt8On23oFpiL882fFzRwWBJ9EAZXUkaSr9k8M6OC3vwYbQIqOojo6LugqCw==