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
- b87356276d75e39907629998d80b469fdcc4e09ccea90d0ebdbb26d74ac280fa
- request
- 6e183ed21e4d4a781e374f540a0d67815c19d231a0b0dca8695b51c8b04e8c29
- transaction
- d7bf7683aee3fed0900e6207007a15b02338a71bc95530b60ee44f7b1703145ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1043
the chainentry 1043
- sealed to the entry before
- c3dc34db79418b85a6aa9fcb59111e477a400f7c18984822cd414a208f2c62f7
- this leaf
- e7d3543eb2f70ba32d45c6d280563e3218e48a23d422940c7e7c2ced8a81eb6c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uNT8w+heTITauMEWM5OisNhn7MwNt+Z+Y3LTHxEFSIOHZBUE0nW/QyR0OGmMQOtCu9deF8URNQ5UAOOWUqK5DQ==