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
- 01997d137d57bf722964e0f2b96fc914e49114e76cf4eeef58212e87b8e2d004
- request
- acd0ecb543af5b8fcd60fee4b8ae4f88d2f5506df0c57180278c0a1cb738fd9c
- transaction
- 9f6eab10a4f8c534c953cb24e13d5bcf4606bb717f11ffbdbbe61ac8b02c7ba9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21985
the chainentry 21985
- sealed to the entry before
- d6db8303791d87af21fd5fccf051d32d3d5d35d69f6ecf033439bbc475c1e779
- this leaf
- 757afb468b3da32a2ef41d680865d133c05c8ec79a71790904583c29eef648a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EubdLl8fTpEdRm8ue/WIqYBEjhvnSSAvdfXvaPwpon0gpRQS5CxCrK7xJiF9iGVLC5DzofrvdBG3NGbaqLlVDQ==