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
- 3d41bf58d758e1c709b8f722cd6215ff2ea467cc31556b346dd238eca5d44c94
- request
- 44aeb0a683284bdf58c9f3934c148925bc6acb6acbf095f35507c8fde4b07c42
- transaction
- fcec3cd978ec5efd13ce45cfe37161d71dd65b185a79c8389e13f716e952498ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32923
the chainentry 32923
- sealed to the entry before
- 57d8d31edaf01963877dced1435311d54608e6f3a8d9bdc48c944fb33a33e430
- this leaf
- 2622926cb661bcccd45bf35dace57b32ac16ea2f56c2b750b079bc37f8d94150
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dHaB/35oVjt6wyOfdQUjCAXEu0hFk21p6RlJS/O95Y6THCbkaVKrRQN6rPSVAZCOVMMaPLc15kecIzLq+tmJDA==