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
- 0fab5fb0f5453ad7dcd950acc6e2434723b7953476f6f73f9e7f852e21a4f2aa
- request
- fa5030a9326a347dc3cd5080ab3df87c8fff77f1edcad0e14c168147f66da8c5
- transaction
- 58e802f51a0b62dbdccc96ce0044aa95e326155cfd301014fbe4c2d997f63c44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45722
the chainentry 45722
- sealed to the entry before
- dbded4912ba0e6d448c0d26019b9e55aca5f9b469a2f690866472be02fe5e60c
- this leaf
- a475a60d1a6b1ddf42de67b700176fc9207fc42f85db41ec2f00624c5b072a3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2ciDYNuPxUZBBMBpw5tJijsAoaObnS1tCcxGonsVjxBTnOVMY/iqNeoIk1cMhC3TefqO1F3gAz7YbztnIFlsDA==