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
- c436007231a9abf235a9a7b02f26e2a23020ae97f0a46ad62b5b58a9f02354d6
- request
- 07b17f9c0af984022d27b379c490be7e25f4864028ebaf94d9d341cf1bc4e505
- transaction
- 65e1d88f313047c0fb2276045fed42255e52546233436f44d4784fb9079e9e2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58954
the chainentry 58954
- sealed to the entry before
- 63727b67097424fe4f613f01a12dac0e2dabf17e9f46cc1cd19d5773bafd3360
- this leaf
- 80c90024ef6b8a495b7bded9daa0941c2b49f7bb4d4d1375c018a06627a993e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iERp5Z05Knmd/G2Kq3hp0mQH/lMLIhq45LAfLJkE1a1kp7+akt/rPqZI62v7d5FCSLvWldEmicvuDhUGC9OEAQ==