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
- e9d6a57fc689985b8df0f1123fc6e75d281e2ba73e29eae5d4a61095944f35ed
- request
- 36120cb01910d8f10618fe62ceb9520e39aabcf8606249f0ad74417c8713d4ab
- transaction
- 57da5b52add4ca9e98b1bea07fb3608fe99389257b77b3313e345950b3a94073computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35711
the chainentry 35711
- sealed to the entry before
- 2e34b497a43391d673a525a2edc35ec6598dfd1d6556c69397f17ba6a99e34f1
- this leaf
- 3081b51197c734a7822b202cc4b1ca28bf4f6cb8bd4d718de9750bec71916f82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d/KBIxizeLuv+rgi6LURl3yNeEQN8LtwUbhVF+HG6yAfRuX1udXWRIAv2Ni386JZskbKpZsDkp+El8Sqy6gjDQ==