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
- d3463543ebc4e068ac9e0f7562d7891058d5566054d0d92bfb25d86fc5b8b821
- request
- 467f05c0f8624f24e2d5e7db5ff8062ab60bd4a49b80773f3f7fe68b8e726e92
- transaction
- f10f5fa7731df2a5f5bb0e17170ac054b9b19c80615be930f898f691a65e600acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2645
the chainentry 2645
- sealed to the entry before
- 396625df5cf29df3782bba7df7dbd657932acf3aea7fc56a504dec755373380c
- this leaf
- 242e88f397b15efeb2569b6705d7429799af20300a48cd2abebfd6b24780c46c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /BRClFGg0/f7zVkKFEKa5POnUIJ2Y5va/gmxqwtFAdQauyVPSo30C+VDkq88GXxypiJAmFOSE7zfANfX10LYCw==