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
- a2017d2d1cc88a3c2de310eb7987a3fac38a51f3a540a75576492f12bb125437
- request
- 82722b385e27197f3de02a0e1a06e69df37e879bda1ed472e29aca953f4a5cc1
- transaction
- 9f53b745f53ec3330118c80b084d6182deae7a3b80cbf0d510725b03224b0277computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72243
the chainentry 72243
- sealed to the entry before
- e65098f6931a4f58baa18652ec2a0a0ba38adabcfd99234f5873ee4eb64e5d65
- this leaf
- 919fdedcdf86a4f1ca9f81cf34dcdf26d772e6d9c2e3ba7ad073920bc3c74566
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eDtTRGtQR7SiiFrMUkr2Mq7TVC3yOzjpDEZvNH6Fr9SWsfZ8qMDfZi9T11/lp55YXYWyw5OzwpFxXqntIk68BA==