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
- a5373434963a11d88030cc5cfcfdcc29752dbdb6fd4c61f21cff6288e3572946
- request
- f40973fdb470e2b36ed8655330bb587b7612ca35537fb59eff03c1f290cab6ed
- transaction
- eab3f5cff618bb9e0121861724fca36d5def1036c1d7dbb809f054e9a1ccc4b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24989
the chainentry 24989
- sealed to the entry before
- e6ad91fecd10215f3d2b098ba6d05d1498b6ed229e723735f4fbe42eee0b63af
- this leaf
- ddb8e3f9afe23457471d306d579e7be5d3438e8e545dadd6225eb0f7106290e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yv/g0JE3xyI2a+lru4IwvDXeTjhX24k5itImm44/FPEPau4OIlem4wZBfOf2Oaed5jnSJGuyp45bv0J2oCCuCw==