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
- 336a0ef5686ad7de899ca0f16ba64958a95c07b893f1f4fa452d5b5f74a22b45
- request
- 6192424b664893e95c10b65d3038743f160696297284b2553fe65ac2101c500c
- transaction
- a6f3e59ff292dec887ab4cb5403d68ed7b8d739197e0b9928b828fd542733a3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22212
the chainentry 22212
- sealed to the entry before
- 186943986ef0c0bfb1469df714a4cb01c72a8d3cd81143db9f6ff6888bff7c28
- this leaf
- ee02404868e6c7aca53ae51539f259e0cb2462fbb8d15e4e89f9ca8c5b92c492
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M/bPmixgNAKqDtL4jEcIfGf9BkK8OfC/O8HZIohtNfnPgVnIcRB59Gh9pm9SsPPdb2vvmlPhKSLjisqU3eMtDQ==