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
- acd953556507743c8633379e2a19bd7e7a27a47451eeb9cb34f4a743c1c43cfb
- request
- 0e6c739de967687767159679f115f222df9ad071d3d12438be0ffeaf64e4f675
- transaction
- a913c40324b0ab4a3389126e07d7aa339bef6b99fdf05e8625d6399943ef6dedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24141
the chainentry 24141
- sealed to the entry before
- 7dd1a3512932cd7bc92b0f3612cabe323197280846fd80466ef78b554d7d4b39
- this leaf
- 20a2a6267d3b37c536cbc725fb88aacd98205a0d68a8a46130dbcaef89888c72
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YhxjibTkb0cFq6w7IwJEnWk5PFyplABE0TUriq/FqwCADBc87powQcg3goA9x9N5QraBOjIyuic6Nga3sqc2Cw==