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
- 7d08f66322984c6ff49426d046a2f52912902ba3b28387160d656b974b921964
- request
- c840aea6895023f6819fbcd4a7ccc4b1df87e654ee040f576c77bc82e85a98f6
- transaction
- 79e9bf1105ab40e7529adc9b441fd904e56a68ce5b388ff2d76e68ac9e668f92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37910
the chainentry 37910
- sealed to the entry before
- 3041bd60f00b4b9e81148fd505741077587eb6eb9522d4ecb78880107b451e61
- this leaf
- f825eb0649fe5f47e42d213cb9845295afab0852f34fe838a4263d2fbc4c7a5a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WSwRjJcc6QT0jl5m9H32iOpbbDoMBKxguE7eGQUSd1qTTy42POaBZafhkBtqOCrMg8uNITIANZnCcmLMFRJECg==