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
- 5b4387613223bfa76c4768174c6f576640948a362a62bcacd4d2b0b70b57fe9a
- request
- b921048d351a02988644ee67fcf4f56de99db011f30a338dd71e6b6c35fe8b8f
- transaction
- d2be8c7ca8daf6a2c98ac8494fe7116f1839b9610b7f13a76aa822a09166896ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13809
the chainentry 13809
- sealed to the entry before
- c1a21c6df35c02c2a14ac5f5da66357af4da23f128dc96372f37bb63b27b36b0
- this leaf
- 50cc237825e8f3adaa7fb18f118b03d2638abf816cc6f78a00a7172f764236fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pbUh66BxOaCFNbjQUXZOzmYLetMDzupeHBdS7x3u+HnlVRkBI77/dqN602qReEqdXVYoAn96KXkiSCjZPlK1BA==