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
- ffb346b2c0af440347b31a8fb449704f13d13e8f66c03f1755f6bb69157baf85
- request
- 47a5e828efe1a45459983321b0e1bbe20bc9abd91609bdd7faf81fdc973ebe9e
- transaction
- 9dfac46b50acd970367a31ae44b20fe34bb784fe878625c54ded5f9f6cbc6003computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32294
the chainentry 32294
- sealed to the entry before
- 4378c0634267c1b59ddeee86e37341b9264f78ee3ae8537ceb29c7a6007e6cb9
- this leaf
- e3b8b9063e25ed6e767b39f01804b1f8d81bdc7f0f956b3e875a47020db31ad6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b7u1520plYVILoYNaUee11iQ+ruO3kS0kDn+mbcHKA4kFbXQEIFRfIprt2uEm8UcbifLvkZw48DiZSpSOjw5Bw==