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
- ac7d0524090993da2402c468236bdf431647a0bc249845a7c06f3596391c6f12
- request
- b0cab4e75688ee9fa3ba847134c108e20158205f00ed1f07e202347b4310e234
- transaction
- c3e0b0c381325debf993e77007b2128df691f6ec49b53eacc1c87eef3f8e7466computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41214
the chainentry 41214
- sealed to the entry before
- 3562e4a8e093a08b038ddadfa124792f647fc9f1bc0ac1fc9b8ac852ab58dbbe
- this leaf
- eaf9662a048ba7466aa1ecd25ed8559e999621778d06cebb3da64f6aa56f1f72
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HoMwG2joKeTgUezLgQD1p3u5iuANpL0FQu1ggMNvDVyGYx8JvcyVbdQEHcI92z2P3pwP9OYphQCoFiN3eDhoBw==