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
- a947117d1cf05310ffaea0459a25bf4507daf7e5f4985376de22ccdcbb3bc6b6
- request
- 1e02b1423bf7b61e841fbc19a1c136d45215b9b7d01929678e27a8d4bfd3090d
- transaction
- eed8e012f68fa0ff52eee29971cbd747b28eb9c532fb7e643ab827a817132eb2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19467
the chainentry 19467
- sealed to the entry before
- 3cece71f2221d9a4c00ba3e7eb14ae8ed74f904f65626d9dddcd64caae722157
- this leaf
- a728f056581c8e79da5ac41b03c6edc5d65a537effc4263252da6b2e01208824
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n4KXAkM7ZDKL3Kix0ZYeutITVOnwksZ7udtlJUg8WJJktI981OznsM8pPMKidfJgzJPP8AdbrJrFbPmYHtJRDg==