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
- 99e4d7782fcf8bd241604c00ed2930fb32581427c9ca0ecc87340ceb438caaf1
- request
- 651b8866321c37e78c83184a822e2150d8c693078974200b65a2dca992e358d2
- transaction
- 0942b3b48e4bc757cd51c7ebe062759436926a420ed0be3db0105e9f3e0dcc79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5669
the chainentry 5669
- sealed to the entry before
- 72012b236e1a2a9a8c3e06ef25b3b1d2049ea918caecb2c38d024332fe5a904a
- this leaf
- c595a3e4b7aa186233e777a92919caf16769936e7927e90667daa332b8c65dee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6ZBNY6R8TB0J47MPvDu6Z37lf1J9iXj0ov6zqFmjWPN80u0TgGIBCnBpvTBbimd8BLbKlCbZqMyjSz+AdGDuBw==