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
- 2ad361b76c7edca4e32fbfb7d4f85b0af66ca0bfb4d8bb3ba47421c9bdefb677
- request
- c2a9b5b32137880f1f135aaa3f701dc8f5a22bec7d6933ca83752654fa332c11
- transaction
- ba572f896c22b2d06c11df259a87367d92a1637512c6981ffcb8c76ac15a3dfecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52460
the chainentry 52460
- sealed to the entry before
- f12d28d1e1b4f1269294e082528e95323661570f7de22c5bf03df0fd05826218
- this leaf
- 4a8d2d9beec047bf693219704e201be2ada2e285dca5395d557893d779e79d9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XT18295SoNN9Nsz4TJXaMNPO1AOu+v8PxDCDYlxiPPhlwCQgnmLPKyoGR6FN+6tw6o2Yf0e0qQ0c/PsfGRnVCA==