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
- 404d8902e68956664379cf063f6860a84248c4462096734f54c295b9336556cb
- request
- 82adce039c26fdcda9c878e6886eac074f25dc192b1bdd8bed5d2b2fb7c88627
- transaction
- 1c27edb0a5efced0cbffc953d95ed466605a4948819a9e47ec49605117be889ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7014
the chainentry 7014
- sealed to the entry before
- 6891a9cf33aef83cb8bd6ff26273640a098cb95284ff2c586d4cb4403b4e2254
- this leaf
- e2572e018927ad6fdbb5ea855d9696a384c573b00de81aeb5d2794a54b543756
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8r1koOYAGBr6vxpns7arWCfgm4Pc+EVMeX5HnFNfiVVHulSkVe2JeXtxNY0ze2KUICt9AVN/ArqXpFbKLQevCw==