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
- a8c709b272d3d99016f91662bb3b818202c981fe50de74fdf0977bdfe3a20b2e
- request
- a13b127b35eca9c0804390184226a381a6a7fcb184bc2bc52871ac8926c93676
- transaction
- 4843c8009d3473f2e529b769be1c25c94fb33d880be88206377b94cd93c2f97acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21717
the chainentry 21717
- sealed to the entry before
- 0206372108a7632d32f9c5d9671b6238bc093b6cca04c55cd318737d20cc422e
- this leaf
- c92104dce0b6f073b9596b5635171a4517df1b5cc93e59fc83e5fc423e70cd13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fOKyY2BNHH1go6X8dXxcz2kbDEmd6YRa+YbASgwh0zvG7S7uRMaFjv/QZJlUi/OHUAPzU9lB6RZRqmw4NneKAw==