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
- 0eb766caec96ad4bcc954fd44db0ee00bad1bb68bdec8e0a93d26ca53a5c2efc
- request
- fa0986f83eaeb426e46f2ed1e1c6753ae709b0f558777ec3fccef24e812bae22
- transaction
- 9f9a955a090895b291b84e5dd11e90d661bc0e3927d10e7650e5828b8fbe58f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75111
the chainentry 75111
- sealed to the entry before
- 70ecf73d144f1f1f8d5ae6d27b99e5422d873d073629b8a8dfcdf81d6bf1ad68
- this leaf
- 56f793b3534a215fee58392f23b71d91cd3ba1d1426b0cfc3416a8aaefb12650
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aYXkYMH4e/c46UT81+Ajmp9HX7ya1hC9sIPXOo6M4147pllhe1KL1QtyPepcolwaoEDNbemiLBlVRAAd2f7tDQ==