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
- afe711fe9d93a0af82e3b911d71c8ac9c42faea32c0d0cbbfa2cc6714fbdb5af
- request
- 9242c76aedfae934cde1482f4682c5d2f71effeb4d2af7dad7b739225de393b5
- transaction
- 1002cb72cf7df3bcf9aaeac17269d44021ffb373c26468e87a2930b6d90d12b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67028
the chainentry 67028
- sealed to the entry before
- 78201d70e5da8c97def45be00ac6c62c6027cc154fb59ab6b5b1fa3d0d84f9e0
- this leaf
- 840b0e3b747376652647c6a82a2bb2824238ecf74db513883b4a97e5fde8c1fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hlBvYoq7UocsAnlB3Kp+pECnlf7X7g04Egs3fRLCcyuU9SWf33zNxQC5GcgkzWBMN3fG/gTN4tlWv3xYY5vKAg==