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
- 8ac8e0d7f781d672ba5ebb8cd448b10065da0c880ac2e924688356cc2af62f79
- request
- 6c5ea7992eb33ce4b6834bd199a4ffee42c2d592e25ad31b68d0fe73ed0e73e4
- transaction
- 0fb81f81a3eb3bd6e09a35a57978e19b448023e9e665f7ba9482768b9e466507computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32410
the chainentry 32410
- sealed to the entry before
- 3dcf34d3eeaa7fa2b44f37331ff94f6ae29ce31fca3c213d80c5d95d37a7f794
- this leaf
- 7c61254d6053707676b60ed1c7f48231bd4c4a4d376b33931bf451bcd6a32238
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oZEFHkXCqKHlA7+F35UVMGkNVcNNScJcYoImpetmxNAAoWqi8zxKqLa6HCQ8rNKTRitfOSdK0EkyIY3LKBeTDg==