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
- cfb860da397a3c762035af5c863f5ad96b3e6e7cd49d3f182da7ef7675148772
- request
- de4b886b63bd8922ea3daf6dd8fc49062e86afd6e568adb306299e3db836beb0
- transaction
- 4f389722a3516ab8f9c33a52a6a09a81659faca448b1a136672c15caa3050730computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1765
the chainentry 1765
- sealed to the entry before
- 970f025418ef5caa80ad9e840cf9840da52955361a28aceb08baca680e21b550
- this leaf
- 24407d6a02930a139a3ba013310f13167096354420d2f78de04f5352691df865
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1HRBIbGmHxCxmEldiaERoCDopCOMTO+kKCSB0CyLmtte4KJdwbq8+ZiorviTVV8qJTxuV2gwUJf4cGIGWbVxBg==