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
- 5cf07a830e9abed7c8bb5db8eb564f2d1a9af4c628ceb131190c790058c56d77
- request
- 690d0ffa4f63e6f9fcd5ab594a2a28100a5e85d451bfb9342f6a4ed8611bbc8f
- transaction
- 254c68457cb7331024eff60cf4a3ee75ca8963359924b1fd67341bacd962b349computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71912
the chainentry 71912
- sealed to the entry before
- 51c09cb750cfc24147aca3f1c5e8d16cecdb17f1bfc197ad817f72ff13ac9e61
- this leaf
- 2c4cc4c1bf0a599b50e582398da062810b2690e0a0ca2cb2da41ead1ccdcb1f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U86SpZdxoZ6ksokaNBEaoo1TJeyuB5k2Qx2dwNlqIxIfzYYgu2du1+Ve0XzHv6Hl+EtAdTFqZSGBMT+71pgDAQ==