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
- cd6535bf0cad2a149d8a279108ecd53ced3cf330dbcecc215e1c35c9ce77bb2c
- request
- c66e632695d825ed57809fae77cf256c89aa1d847a813b1b66b5e3d6de858b55
- transaction
- 3efc7d0cd0c5cf8c331dfa2f8d89f2594d915cfdb0a28919944809b96b272deccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62514
the chainentry 62514
- sealed to the entry before
- 1028defd8246da5bbb5570c4a70320b52249c26662273a96c97f2d01485b2202
- this leaf
- 8cdc11bb0bccf7439432c3869323d1088dbe2b67ae85f334364c9d0a66047dc5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bKL9HrQaitEOfjA4agLg5H+eqXyhI65vnuVI9ERs507k5kRilTTo2PLR4PWo0hPFxpoO/vImOA313XWHPz4PCw==