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
- a27656c1700f129c9e2105be072ddf4ab8817b82729e3e3fc71ba1f3f7342fe6
- request
- 52c7bdefb1864de6f1cfb25b4292a65598d1033aa1a9ff9cff9ce70a7b75348e
- transaction
- 850fa0bef0ac2650f582a9c4db67035c11b04d58adcdfdf2b9106e579ae47462computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20974
the chainentry 20974
- sealed to the entry before
- 8bb80e6dd755f3e3b2aa68f106fa7b71915145bc21fbf697296144b5557eadc5
- this leaf
- 66c1c87d19b7d9cff764e4eaa748e672a8de10c99a297a837c3144503d2776f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2E1kcjpQcoNksDfeQLhPmkXj0ab1EhF3WxiIsNORzVcwxtNCJhUwOMP8IWJBp99Da280TFHLcKdtvttDRnUGDA==