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
- fb0d575d33d223db9e22c397e24181283caff8b99f154e10118d8c4425de221c
- request
- a8250e0f10696cf7ef7efe8628501777ac18360a0f5cc4b53096f61e9fd022ba
- transaction
- ee1deff4760cf2d27d6d7fe94931857f9962f305eb741eaee8213412af7e2251computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75755
the chainentry 75755
- sealed to the entry before
- 9f8a0425f794ee3dcf3943e27b47ac762f7d799dc37266d4dfcbb64ee5622c34
- this leaf
- 0de626f728b17ed9acc9f9c59d74b2f839a69a7a4380a8e0e131f0f7963bba01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NGhtoGdiaJDuclQfoxW6jOfkbwJzdxcUDWwpnukZlwhTzxppwfxBJMy4aUHd8jun17+t3k2b3z/crmL7e3QHBw==