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
- 233506179dbb7ac55ea07c5e9de2ba6cbc09b3120cebcd07bcac1ae701547681
- request
- e7e18e11a49f877c3ceb3559ed4be5b4bc72da2c84471579a1f2c0eef6e3364f
- transaction
- 7f6d2a7ab741e27fb0638e0068867952559b47567bdd13c4b5ae9b2fbb5e0411computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64168
the chainentry 64168
- sealed to the entry before
- a9e623f21656fc31f09a5399e5fb285308de34d15152b899b764db4a1e9595ae
- this leaf
- 71fa82be284e920967f45527712f2680bc5146e8dce0eab863d406d3c46a315b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LsxSCTSF14aGenwdF4iKfNP8HpFcIofeegwKTkdhRYXmuq7jBrXHYGTkvp2ZUlH+5mHbFlVw2p5WH5H2MXZwDQ==