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
- d8a69482d5ed717a0c4d3141095a0b4e6b9c961bdb10f0245975c116827a0ebc
- request
- 4e3ac8be2a8975428a38bd64f6f4ca23e4d78b2e4bd24bbd156205ee1fb26158
- transaction
- 891043ad2cafe91c692a21c59ccadaca268404fa076bd155bc8bfbe4e0f5a497computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75639
the chainentry 75639
- sealed to the entry before
- 48c9c286bcd3ab9d936300ecf90beb63f741d6e66e9390cbd0a6c00ac822f1db
- this leaf
- acc232462300323011eddd4c9f746e66646886a044540008f7a08187abcd7ce1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TLlOoNQYWwgkSFQ5pY/Brlnv5eMRsSDiY26sj5uQ+rXJDj58+87DmULvEZ9Dl9PpngAuUKZt+24TlkdjA5vvDg==