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
- 6f8c55842a9c3ec3f986199888699bc0e2f4486e251d8516085e100eb5161745
- request
- 3aa2b391c27b9f5508d32f67c8b8e25c54b86ccf233701a24833dd076f791360
- transaction
- 6e67653a366b63da8fb48ab57472ec28b67e43e499eaae6284c450fab75e1421computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20899
the chainentry 20899
- sealed to the entry before
- a4424dc01bedaf8bc990dd5e771720cb02f114db7d00c356e0691f7a9267811c
- this leaf
- fd69db78aa5896be8aaf850f23b3eaf14b2175ddb809ff3da7788e49a75534bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aCfgqlM5/WDz2QaXwZ3hwshEwAB8cof0WKa8brIwWueAlgVl0t5xFl9PLDhywcmlFg6Q5kTOXN2Zs5113bohBg==