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
- b0f3abb93820b98abb8a520b693488e2c90463fee1aa2c876aac49862e28bbc1
- request
- 002ed91f31a167f031659066d1b0a35ac25b3a617b251556a3788942626f9978
- transaction
- 7fec395bc30281f56b04f045032449789113cdbbff2405ad7906c3f4e974a136computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32228
the chainentry 32228
- sealed to the entry before
- 4c5c0e4e5a459609acd3c4d2c8eea3efec8529294e8054f9fb569ad4c32b6e4f
- this leaf
- 42681b1d269b3064b6ff4d1cff0f83d4b5ae3db8be389652c4b08623fea4a815
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V3mc0HTkUZ/S3m5wlVarYaYL7enZME9nnqP+cIS60/gPviK1cVN3nm71mV3Q9XcBMsMtXz6+XdZXjX+qjLb1Bw==