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
- a0049e1cb0e189d7fb78742f30ebd2e94e67db793e6bf05b98ee8aa22022661a
- request
- c6585d43500476838bb122c0ff8bf874b0c01817d2a41f1b75eb65a2db09a9e5
- transaction
- 816d6fa0c51106bafea617631c09f41e02655969d8519ed40006c2fa334c9fe6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2545
the chainentry 2545
- sealed to the entry before
- e034612fac3cb2a6917f1a160b0993ae0c2894e34aefb4472501a4c9ed391f9c
- this leaf
- 21f7db3fd35db6f57c611dca1f97b7abdc23a74479feb1dc310a90c0896fd456
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3gSxALbaBGSCaxXOKOFpXgx2K7AcAVoUlcsXs0HAcYAL5vIPP8o908STZ8AW8eFRU7+vFx1ba1dxaQPJQe4LDg==