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
- 92579158ca95f097297d86d5b6a2bfc36c46f002f1e74915eecfcc3308206220
- request
- fd3ddde38b4338cc046272bab329cfc9c5d63e3164a75c4fa247c475d01dfad2
- transaction
- 40005b905464eaff19f530e876898e655c57e9dbaf98dc3005a46d7761d3d25ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5107
the chainentry 5107
- sealed to the entry before
- 0b782f20711a294892cc985658495a0449cbcd65226cae9798e10d0f768180fb
- this leaf
- 15c047dc0b40ebd5a67b4000a75c7abcc5e8d893aedf1ea295a6ccd4c3b6b85f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HSis0ze9Hljpm5bqbARShzsCI/NCkNkz7qEBhehyefDXtB6kUE9An77S5nBDAsGfrssce+gk2YGM9/KhiM8OAA==