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
- d18470c3d5bef5315f3814b8ac0fa71b05f5505da3be1a9bfba6e4819cf46ba6
- request
- ed04f8b446e3de5d15b0fb58a742d111d32ec878fd7ace4226974431dbbafa88
- transaction
- eded5754cdaae3de65be1bc5c98fb80e128777c91602ae984db9b7950cb0ca0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16052
the chainentry 16052
- sealed to the entry before
- 77ea24f0cea5b8915c497fc211268b0fd52a47bee724b3525623a53573c59011
- this leaf
- de3d1635913990226aef79498629299db3a30b51116d4a5f3093e1a9056bdee3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1pJ89JyHOtv5Oyv9nUlsaDmRazhsD5Nm24swCXYXWjllhvVBEQXE1wwAnR6Ovxe6nOP411avhWB73fLUwUgbDg==