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
- a37cf0b6e42a58940ba6c4afdf74dc7dea1a9146f63b81db28651013f4198c51
- request
- 037c6232ac02fe0eff74856f72d0fd6eca991c106eb46d4bd462517811f4e84e
- transaction
- 6ec162e377b83450ab65a23bff9aa4dc56502919d72eec94ee006b7a0a29b710computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3646
the chainentry 3646
- sealed to the entry before
- e6f6634cae796645a7a11e473c0adda0d4d6c2cb1a85175f29a1fdd6ea217086
- this leaf
- 49ba353bbe318044bce042e837539b8c07f834fedc58a8728c7ae01f55af1357
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l4PI9iMszIp8Apf2TY6+nvN+nGD8EJRwPNTLMvIARt+uDdVko7vIYg7zFwKaDQPMVHwRINsOBwo3n+59tMPhDw==