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
- df3c96d42162668db8c6a3eac2dc5588b18a7f786dd6cd0fd5f46af2150b404a
- request
- a78543b7b1c7e9e9cf7f125b4a985e61c8daa7ce9961b54f621436234ce532c7
- transaction
- f9e29233d021a8eda1ef8922f42b296e4e43b4ccfb406a16cf2a0195cadb534acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76960
the chainentry 76960
- sealed to the entry before
- cda924819a892fa4ec67adcedc14ce469b3c624726b675033d29486375e867f8
- this leaf
- 72693bbd1452cae92556bced588fa9687826941aebdb16b6c73ceb0c3bcabcbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6xGto8CT8vhbHnQE2do7hA42cCbHtqMUewMJETZHmRLu08oT8sWKuhWAQOIQweghYFaBiV0SrFKVZpeJfbd7Dg==