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
- 3ab3030beab636135b44794dabfa31466e1693573fde251a9683b868457dd272
- request
- 930265f9f42faf829f478897ea8c46f8d271fbae7b2c51422e11e9db67848be3
- transaction
- d7f8f4d5c9ac3c146fd282184f60ce5eeb3654b04f1d5b4c3e464c03eb6b07fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7503
the chainentry 7503
- sealed to the entry before
- 3be1fbbe1fa95e9a4fb849fb7c875d78220df07c92b16351f31cdaa028d7ae52
- this leaf
- 089aec5a98517cacd8ed9fed2ed2e288af9cfbfd19ffaf8ef3068dfe360e7e53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V/o34QbvP8kx/Ha5uU/PKVPvwCXHF84QUzccjP8u19cbe3dNMQ9c6b2EQkcwcpq2S6zm23/LA/9tvB0hvlbJAw==