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
- 720661cc2ce32157b46c0334d68253476ea3d6627a84ce1eb1f31cab8ac6e406
- request
- c70c3526d35a085a3cedd695d9c7543829216028f1b6f750a9f374c9dc10337a
- transaction
- c01bc692b3154d70b985062ac48d3336d297453c5b7ab76f5b76af82a84367f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 181
the chainentry 181
- sealed to the entry before
- 4e857f8a81c44f7bf2726cfb2c503d4baf00006d07547f1689f1d73ec0ed57c9
- this leaf
- 0b3bead9400cf81c0065320627a75072a829df42dd7ac2ccb8d3a66e73dd2e94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OF+KH//W6NU1gCZbmD+uTcx3cGhZHTFEruOhF8eSG4axSGvC+QI65zQqTEhSZHLe7xSuIqWmVO25gLFkv87aDw==