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
- 53a82923964e2e388ffade00767f7f6ece258fa400fb5176c5d9dfb3c4fbf0de
- request
- a02861635548cb19a4a4a371437c8a57a098bcc5d0808cb03dd90750a68211d0
- transaction
- cbb3cebdd9ae7296e0feec25b8ff648f3c2ebb55b1d84b1445bd5b735c859ad2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10667
the chainentry 10667
- sealed to the entry before
- 59502983f576f3bdabd2ac795b362d2b233a71269dcdcc02574aa5518a4eaf3b
- this leaf
- 9e63942653d619e6d84037146dc5ddab4074e82b2c531ff1d0749f9ce570fae8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P0MeuLssvT22adrlrL6POgC6ayZZL/iycBVRCuu1RDYR1mQow6UQIhHejf+zKUePkFpJY9i07zxc+X5SH3Z5BA==