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
- e4e2aa0c107cedc7642c7dce79b4bce657f1e7457a5a305e31287a3531ddaf68
- request
- eccac75f667a8f265c06d348f1c4c05cccebbe2fbc0461e6492c77f5869ab576
- transaction
- c75a4a2ce70d64b6836b105040d76c1d334641e90f50e7785d9c72bde8ea9ab4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45364
the chainentry 45364
- sealed to the entry before
- 123da72f8c2aeb136b0c1a394ce159c81538baed16a9deeb0d22a95ae717d9b8
- this leaf
- d6ca1faa7a7e8d6a46e0b58c4698ab544926afe9e65fafa46e3036e976c0a17b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TPNNZGjZDmB3LYvS85JkEAaUqkneLfa7Z8CinHBnQx+e2UfBKGOYRzXX6buaPHJIp1KMuMZZ8nHeb8qj1PQUBA==