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
- df6d8f3b3f5a72dd26ebbe0d7fc934e7ebafa635b1224af5ec5654a0d1ba7a14
- request
- 16406111855fcac7a59610ff58f8ef9e765936680814a6d5eba74359738f3302
- transaction
- bbdfa3c532a932ce1ade040e978d032f7c0df90ca1cc641f4427ce853c0da38acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65280
the chainentry 65280
- sealed to the entry before
- 43fd81a0d787f14192178fa7ef427955ebad4eb47ee4f556b81ecbef8fc8e385
- this leaf
- 43c29b7aba4e653ebbbb471301d636896056d8195111177f44b73642397a61b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Utg80TrDGu7Jlc1cAi0IE9Q9A+VZbXIe3u109rSGbvJluy3onqIBoxxXoWPUgjN6YBSqXX+B9UsN9B3JMrD1Aw==