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
- 9587b0063d7758a5551c246a56243647b2f2338c8bb9b28ccc80efccaa8b71cc
- request
- db9726171356381f6d3d03714432797d641b3b311397c60be62c40e732458d5b
- transaction
- 42856af719fc733e114cded7cddc2c2f1be22d39bc6b6e4b46fe4d0dfd8cb0fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64476
the chainentry 64476
- sealed to the entry before
- 9908b14ee063953f53b373238f485e7ce83d0420c2ead89d4cdfd50cd6b5c154
- this leaf
- f3a765aff2f53a2b3690f12f3d328ba14dbc834588161eea84410cfcfaf7e49e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bppz6EQ9DkPqxxdDqkvxCk8Wd/TwLdOaJGbYbneFeoVzRME++8425qXI0FHPT2DXo22JnsyrFfzVVe6BhKFeDw==