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
- c93816d783e37b0054e0568b6adee8e597ee4404e31c70bb99424f0918904104
- request
- 0a300d1201554cf4bc0c5cb8321c748b38e98d5b52beb4ec17da5212c4786c4a
- transaction
- f1a93cb5d619860ddba19a1d7052158221e0325ec1a36e164b705f5d14889d41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28472
the chainentry 28472
- sealed to the entry before
- dbf0f1d352fcb8688ded5b7152df6ff3c2940fe81cae6498dcffe99d4dd1edc3
- this leaf
- 4a849d2c296e9d0ddfc4aeaa2b242e54a4ba452f54240938a4690216b3383f14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g26ZTHLLrlTXs3GZQ4zevLnsAL4ZDlDvy0S9ypjhgv+yaWE3SrCS+6GLjB3QBuksvz40/rHogUKH2WwGzg9FDg==