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
- 1c811e97ad1e44d98b4699f4de58a0ef342dd6e549af8c731fabd445d858c7dd
- request
- 8e06bdacc63050932547ec468595679fcc9ccd0dd33fa0773e3d256b77c94644
- transaction
- f6d4778032c9701185f185fa734a363f89dc44fbf871981e3cf69e68b4ffd767computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54607
the chainentry 54607
- sealed to the entry before
- 4ad6514f69d4ddc94e96e5b28d87b8863234a8f00bbdb96f945c54aae9d600be
- this leaf
- 1c30f441e4796e1c8edeb31e07dcee11ab49c2d2342d051483ad4e6a579c780a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4UCFvpfV90vUwzaed5b2sAOfawwN37X+5rT1w2gpNnPL/OnqGy/DpLUowfO04O4puu8Iv6ayueCcqDsFZPWGCw==