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
- 3dc83bdbb6f6177fafac7237a9ed9552148a103009eea0a862ccec112f515ee2
- request
- 4d6a2f508c3ffb2ae8411aa9af1a2955d3476a3db4c6bc337db84f0c846e0305
- transaction
- 046fb64cf33a717d272f68eb71d88a04bfa5b73db8dfd577a43a0d05da3c557dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21274
the chainentry 21274
- sealed to the entry before
- 3862b74ce7a479ef9e441ed8a0237c2c94a0185a9886e1db69ac879d8b3a57e8
- this leaf
- 1b66307af27329165a2246cf3fd1337a6cf05f4ee151413a3db33f6d3ec3cbce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3OSwFrnUA9RP4gemNuQ5cKAUNPnCFXBVy0l5zLFspCWjh/K8HRGcO7iA3VnxNGUG8MDavoJCOUso9LsAGC5YCA==