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
- 5e2ac4496d59118ec5c28db115206ccdb5553af37f0396c931a4df9ade52c403
- request
- 47c21e94dfd155ded46a3470361fb0cb918d95e69194967a0842f2d68a1bda3b
- transaction
- 66311363ec89db3937aef83222ce7ff24e44416820f15117ca9f492942b7700dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55622
the chainentry 55622
- sealed to the entry before
- 5b602068ea33c29196a92e47d34697cd163c43c8848099494580e04669266f20
- this leaf
- 85d16937dbf87cf749f224389ea698351c9a7aeeaca5bf479f6944d86ad8af9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n7j6c3TkZNrf+J1ChAlfOBNhCLtYKggcQ+h4onpvmHNrHqIFXj4mxapheqPkDWYNEM4ClsCMWNEhDHHyq5wrCA==