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
- c2ff2f6a3aa444c40be814cb686c7d712259cd4cadfb72a624a4abe684a7896b
- request
- 170696f886d24a9d5327ea20abf730ee7e72bebf0d823d0d8534bb0b11eb9f0d
- transaction
- 874253041b539555760598dd35153ee48101baa93b9c3fb49478c655f11e9618computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1122
the chainentry 1122
- sealed to the entry before
- 051e29354889c0c3e8f700ab2f33824d1348b3e11300ef65594a483271ef5c7b
- this leaf
- d4a640d8bde6407a06f0e2a79ac26e2ef404cf85618a8aee62f19d51f1cbb5ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HA0rkA0b4jX9aC9o41C8J9qmwyTOV7N2TySz+ywkniqyRDtp1+kJAIJW8aPGM6Omuqkk4OzvMZOAVwjSZ8HyCQ==