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
- 7ade5c2168ee4685c70dfa69787dab70a5316f3e4575293b550ba35a3f386098
- request
- 173d3263a67f93dd55e9a32f2e526ba5f1d3c885cf3a7494cf45e779dfd80181
- transaction
- 15f608619bc1dc78ca496c5c8b01416d26988483cb058573624e9e626172a04acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2605
the chainentry 2605
- sealed to the entry before
- 64c948de467a6ffdd1a006f2cac978b33dd9f96c89713b2fc3a2244a8ab3aa5f
- this leaf
- f9b5aa7e50344262c64ecc54bad7970f48f71b1772c3e1a4982bfff2b293faa6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o5Z9w6RxLnQoxu0hxJaojWq0yPncVLqlCfW+MtbcXjaKnF+s8xA1U04+tUybDi00VEhaGhOKk4Q+PsfVtXw7DQ==