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
- ecb13dd5ee76d7c96901d5f6ef2455f504420e4f4c5f18701b3bcccf466085f4
- request
- 0a3783229368a7e3137e4519f62a8356f5826bfa15d9249fbafe5d0086ab6dac
- transaction
- e8759f752014130e19aef25fce5abf4794f41745ef459a3e328786087dd48c1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13971
the chainentry 13971
- sealed to the entry before
- 4ef89ed3a0c243b493cbef53800d189ba5c2c7af84016972a82544dde6985a04
- this leaf
- d5be0fb9725ac8e79320461554dc1c494e67e0aa2250765f8ff4ae1165a9b18d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 23Uer3tTxte5Xt3AD1stYJ4b/K7faEv+uC92MA5IIfryPutmoFvMfC69hoULFuCK5U40FUOzj8bINtKaJIBcAA==