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
- 220040e51eda0c591f0e990a5fa576a64f6ffc63afd780c43bb1e7acbedf68d4
- request
- 0ab534a4c02e6c2dc336c9cdb0eabda5666f46fc4a2077151046d61a15cf438e
- transaction
- 9bc4e7fefbf7cbb42708383864e3994940803d8717b8e6cb613953c018f8309dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2510
the chainentry 2510
- sealed to the entry before
- c1092894b92c6cbd7c30715f5d5594f59fe7b469961fc469f35b9d233683a1fe
- this leaf
- dcfb90f2c5365bf218186b5e9f3851c2fd956fc8c6b9e61c9311e4e4f93f49f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G1xeXl8O0pKTMnytlNWlF9DHw+TcI4JiOw/OyIL5rdJ36fdHIFo+vvJkg4cew4ZmQ0TMOF5SdSHmH/yglD/5BQ==