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
- b684a9185f3522c7b8654670dbdabce01155ac219e9d4cb1581d705b5d01ae9c
- request
- f1a993ef4ece148ee0717abddef2dcd73cda3daf3faf29d07b91bb4c45e088af
- transaction
- 363bf9e77da005867e0fc24fbbf90796f9b23e06a828ced1878ea043e93cc597computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26833
the chainentry 26833
- sealed to the entry before
- 127e8681413a278b79a4315d7d2099443b87a3088c51a5209304bf02cb45fcb5
- this leaf
- 8be651d8fa6031ae8abd20238bd092b73508f94149369f7f645b195016137adb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fe7BFHFVjx1CsZkOulyCBN4f7q2MbpMxeJfNnt0onTMxfkVLtlEOMHWr5ff8fUkqQ+4uDYyEtMyctEEpsWdDCQ==