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
- a2139cd24528852c2c9b14ffdfcba9cb34bae4ee7f812303fdb3b7e6e4b8ef02
- request
- 3c1794429c1e7829ba2ebe851341f2d8a2f5e030a62e0b4aa0535b8eca9138a0
- transaction
- 64bebee5070ade0c92b7c77f3470c7621e302383435bacf914fd1ad56c914316computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63906
the chainentry 63906
- sealed to the entry before
- df81957adb8b8436807e05af65468807d3ab9d4cc01d8861b1d85a0bafe05d07
- this leaf
- c13c48257ceee9e00648b1913f8563bd0d104960078d41de333f756c83b5ac72
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1o+LV+qHOs8z2UskTpCOyKr58RIfOd/igyI9T3Mk0y8ZIiwnxxjtBcbM1HvrELkm2IpjRZL/fzZMXAy/uwmTBQ==