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
- 2bed4e817d66fbf323a7b1b55b69b008c85c4d4f911d0cacd6b9ce49eb1bb287
- request
- 9a8575c03d6dca9aa32c302ca1c2b2ca07be4e2fce240c56f3f5b1857516baca
- transaction
- e823a1590ee6093db2ea330643243b956ce54a4f83b2b3c3a573abc51812e6b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60324
the chainentry 60324
- sealed to the entry before
- f80e3cdf4cb57ac0a3b1192656884aedd765ee18d1966d791c084cddb6d923d9
- this leaf
- 9da5f315d72f289e5e461cbcb9831e86c1d9ba2cbbd0c61b73f78e55469e5193
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qxJkDPnRNpc7xcU7BtF1Cj0oJdfD1gaglXALGpq7FWUCIZ7ACLD/KIAN9NthJmSN6+4N6TZbAEaU7dYP36A+BA==