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
- 7e929b24035966cb4d0e63512384049173bc97bdfe60e32ccd996f9fc9574e4b
- request
- 8adb061f4efccdff92c1af5ded8b239713be5b1158c67a78d2e9fc93490c1cb2
- transaction
- 4b3410fd762f980e9128880c6db3309e5d78e58bc804cd403e9413f21b17b74ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26278
the chainentry 26278
- sealed to the entry before
- d6059081eee1195abe07d267094545360eed0b435cc8f51e824b0c1aa3a3fe2a
- this leaf
- e8c0cd0c7a0472f27dd94dd03ff171efef920774962324206c9bc9a656227aaa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /LMQhDZzodv/xcmQinFcY6GvAdnT6CfwTnMHo1q+EZNGOyabritZfDyAdhmAiHeC/H+haGfMNnBN36MLUGQLCg==