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
- b78c0182d1fad2433381427f77fc208bc97ea5175e0ae8bcc0c2f1c0dbe66904
- request
- 9b84835d7b2080572965429087e77effb27d2731147d01ece20954f01a2b044f
- transaction
- 8a11fa2ed9e7dc2d75a5164bfcb0aca31614337f576daf8b0edea90d8970485ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30273
the chainentry 30273
- sealed to the entry before
- f1860440d1c45da5a46a2dc1a6801714546419265720394f38faba4020926197
- this leaf
- 07f5086aaa0555f3b349734910c1a23114326545ced9ded48d4b89514ee94422
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hu4m5HhSgZmrJenLlA2AhNipU4kBmGFbx6NtTCYNl8QUB6F1xkGig+U1M7wO2kSVwHUCdnisMKj/tufuekfXAQ==