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
- cc44ffd1ea8fe7f073032dbf40093abeb805ab705226d9911a8fb7aa57cffaa7
- request
- b08f603e8b6de814d07bb2e1503ae01d47e5e207695066f3ba22bd0488f6dce1
- transaction
- 07cd59116828177290b2a5ba3f5823eb7dd4c3514874a1a863f64f289de18a50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64174
the chainentry 64174
- sealed to the entry before
- b2f00e0f0e79b1f35c7c633a8b3fe1e6ffac7fa464023f2dced2441f88c4e4fd
- this leaf
- 33ecb963988fad673776ae526bd5b372d298ee1650881937fbeaf444ae823467
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GVEZibckk7Wq6p894ENmpHG7s9osR8c0EjiCsvPTvHtzvOENAACft2I/rFxMMj5adNhSc7oyXQZqcI+PPikwBA==