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
- 8827b748526e065de22223f3492ece504543a65a2c3f4dc347c1736fdcf09d2b
- request
- dc164f43870f32a830fcaf369b9026095f392ff23d9257052dc2bf5dfa223f44
- transaction
- 908efb197705f7e766406239c4a2c7db7075e10718afb7fb50c151eaa6d8f037computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53745
the chainentry 53745
- sealed to the entry before
- 223f4b1b93ea59c876793e951170225be3a910a6e1cf83bf4c1fb1d361395de6
- this leaf
- f511f775e8e2db39cde34ca50077ba5ed8910894a4ce5c4dc3e9374d6fdc15f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tuehknbpx7UA+46q6OZ4Pud0Qi4qQegWqi3TmSjnclbafE6H/LR87bGHfCKUeek4I3664t57+WEFQC0LMXH/DQ==