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
- c3035664f30e998e2a0bad08d427c3513564bfc26afd1894d5d79ac3d668f814
- request
- 4ba230f4690a3f28271821fb40345c9f3b5e1ce1293a95921d36c43f42f9616f
- transaction
- 6053351f6a9fc143731cd8f80b498b84ab40ce4d748ed4948930ea5e4f4f51cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29800
the chainentry 29800
- sealed to the entry before
- affb2abae428389d00ff96f4cd5f96cb894529bdc9915b45e0fd1ea4ecc15892
- this leaf
- 3347d93c3cfb5c1f166f216c721c524a8848a0a73626073a30472a293b3dec64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- POIqtT8x4tl+Dd0XTXrZph8rQQyD0MK+3yl9VPoguUcQnygl8IyLky3CUJDT1Y4vzcwNqfYBahpfsKddlpbgCQ==