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
- 96cdfc3830f8e06ad460b90c5cbe494958cb7dfbdf3ff887487ed5238d2154ed
- request
- 6975946e2efea0e145a4bf806b2d36e0d8033b2b998f2c8464131a774b0c8c16
- transaction
- d08693640230390b2a0a20f2266cfaa863b4035d0963c76d993b43ef435bde05computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 978
the chainentry 978
- sealed to the entry before
- e7417dcbbfb77875b98dc8bcf9ce80230cdcdc3220f3cab4d72b49e63cfed20d
- this leaf
- 4d8432dcde709946fb356af0ccd03649b868b7e66b772f4aa659b838dec94fb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BPZNtuMz4khayDrTb2e8UzZXTaaLETooFMvVGYh1qMdOrjmE1twuV8Ahl7ev0Vrh61lpC7EoL5l8KItFPdeIBA==