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
- 08c643efadd1854aebe324cc112ebed83a6d4f8a4476a948f70c6dea75212ee3
- request
- 24afc6cfee972619766051e9835049507d1c05df4087d7383771662db76ae64f
- transaction
- c38fb5c4df5f2026594aef1a411e4e2bbe808593c722861d9e330a45b986235bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70519
the chainentry 70519
- sealed to the entry before
- 889c1ffe568805aa6a2c62a93ced8c1c65690f4658701bda5837a845f4178884
- this leaf
- a3787fb32f514b1a51052f92ee348482964049d88f0e7e878261309f5bc8feb1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LoQTzTqLDBKmkxQuWbEe08bwhwD8crKRZa5boVNCfPtqAleQmLEUQUgcaeiSCoF3lYKVeTpTXGNva8RZ9Q4PAg==