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
- 104ff66aee3cc9f0c33be9a0edbdbc4bf446b7822bd86d5da47e646fe0a08cc4
- request
- c4551d77194bc86062a0bf0db798187d104d8480904ca0c932147f4307160b8b
- transaction
- 7d46ff4539ae939ad9a99e24c1727d2cabd6e840b58881cf062704f7f501bf77computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52660
the chainentry 52660
- sealed to the entry before
- ed7c9ecbc87a6f37025b186b6aaab5430515c6ae678d62bfb2e02634ca10b299
- this leaf
- db2cf42197c675ebd94e4cf912c3dcbb60145d8fa5b747bcfc21075a5c3d24a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5sbqQPJg0JvamI8a1spKIQPtZDjep9MaRyDYMAY/mvDP06AByGgmGuhy2uUbMItttyG7cjsDpHvQ8NqFkua+DQ==