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
- 7b8f2eb82b11c6fce62486c4dbf79e01484743d3b03a09db643ca0b1cc941f2e
- request
- e7ce3fa99a9530129684711e41f861c6c31bd3f9da2583e638bc4e5a9bf1dd01
- transaction
- 308082bb8fa980bae8550bd75d5670ce2646f68052f2c2b58050eb9777338e2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52203
the chainentry 52203
- sealed to the entry before
- 9c760a5b2a31537b7bb4dc545001f9e57bc495eddcfe2a4a8f26ec3286ce82f2
- this leaf
- 4aa1e2cd0d3a178de37fc8fe7fbcb3425f065f492ae23d1fdfe7034a9d9119b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZlvEk7t6epxNYri/9irasf4OPsryWmUNtvbAMWlYrSG47Nu77AyE0P+LeUA+nueMPECsdG5O9BhFFwW9o6S6DA==