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
- 60e4b0d81a0c85eb729c85a362be5468bc337257df6ee1b41ac228832223ca4b
- request
- fd001707c524899a2f7f75b474128e26e8c53e6565124558076b1f18d5d9358e
- transaction
- 546349f60fd4453d770fc38b39e1387c7bf638fbbbebdca18acd5b8aef9e37a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65686
the chainentry 65686
- sealed to the entry before
- 7cb3117ad257d7edd923369b3f5a2e167cf8781f0606c7aa1c22187d3f8ba361
- this leaf
- 8c4b0506a41440a5057b4e7c3ef29fc61dedda2fd576f5b50cc78dbd1d8e0b8f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b5ZCyElrYdPsgiETnGZGp0a+v334RdFDKAjo02xFwoQGwBmav2nsbXDQefYimOa8omr++dJlerwacdM4PA+oCw==