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
- fee8a2fcc2ebb3bf9a34830e456bc2a5305e27e39114e4309b89f1db5494ab55
- request
- c70735ae4f24448b4f38d4323cc2b937b1c9aa90ec502c95bddd32ccb2e0696d
- transaction
- f331bcbe666546db3fb2cfb8eb113e75e669dc93b0782c6e9df4c4dcc5625663computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2000
the chainentry 2000
- sealed to the entry before
- bc92e70b22c9e0954b7c5b89af28b840d367e5104b2870fdcbdc16703333b830
- this leaf
- 2019cbe52cfb44b213a2d8138160673709fa3255eafcbba182feb53226fd87cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ge111nCLXhOVGs653+VTDuNFJ+E2HhoULbRzv4cjVBXNrOTOzHHwD10z7YAH4XK96TCkNZ9RgC6dALEwXWH/Cg==