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
- 21f92cd367b70955f6ea2f8c1f727032d55b8d616b67e6a0b1a78725423cea18
- request
- b7a15dc46becaee0a612ad85aa137a547401897e4e9d19415552f402aa6ab558
- transaction
- 0871113c15e4d45f19ac52c61211c7cb89bd625e3063a8d2ae3388d8c7825401computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74357
the chainentry 74357
- sealed to the entry before
- 28bde16beb0263e28994fd635690ceca45be7932391a25f0c5d70c8525fa8810
- this leaf
- 84477370645e1c3aa46179a3ba428cea0e2ff342080b55ef9eca35b73b1f3a2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 37lEcBENmDqUMaYha9PhFTCkngsdu10TAt7VYfW/mQiQImJDxu0ov64XufodMUm+hO9zJjofaDzByOxAcCPOCA==