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
- c8df3a0001841c7d18e98a3191a045055bf5a9c9f0e9951ed7817ff9d4a092a7
- request
- 6f9365449f73405ca9156c53e3d8c3088cfdc8f4e9335a4303cf086d62120e7b
- transaction
- 83c295f26d7fbfb327af379c97521992d4abce4f3b5094dc6d9b9272c594eb67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35716
the chainentry 35716
- sealed to the entry before
- 1e7a15052277205625050bc9bc8649564cb83c4847b711403698ff53f9fd6ec6
- this leaf
- 97cf3881ab777d01ab468395d0ffa7606d1fcc0803e3c9f9b17e2221d5d25b1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /7aQHCQYSFEa/miKdFqg6uQY44HopesNQ+eeeeJY5V4TD8NRdj7xsScE0VkjyD+BIB0ooUTaltavoRmSp3N9Aw==