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
- 7396ffc090519e5444f9f070cafcb4cca9d235c011b62673fd1d7c0231b0c7e0
- request
- 7c1ddb01a92609914374fc109d13aebab6c18616b7898f9ed8384242be21389d
- transaction
- 89d5555b89575dd6129803b2a1387b2ce9ab9965926e4029bb19622917f71b55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65394
the chainentry 65394
- sealed to the entry before
- 370fe0f5c93fa0156c993c136f3f10f77dad1333b71cd84cea457e319b20940e
- this leaf
- 181324de8fd8670fa9666c60ef25f0c0c0aeb855adb84841ebea021049bf6a21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z6jMdoXCq9TjqKki1tlqtoV+DupUg+L7VSBj+Lr0Qwa3X4JjLznKGf8s0MC3P+xYAt0jpJF9EZL4OcmwBDb5Dw==