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
- 380ea37a216ad461efc2e6b043decc9af25daf553d83a42f108611a831d695df
- request
- 9f3ef89c88f668b6dd308e2ea27fdf2567fb09cfb42d142674211e86cbf058b7
- transaction
- c44b995ebc40ff8c3f94f3776a4dad768a7ba5cc87282cdc9e66268e1739d8b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66537
the chainentry 66537
- sealed to the entry before
- 6ba7f68f4a41f91bb6d91f400a10047df2b73bb760b9142270810c77274ad48a
- this leaf
- ebf1758b43d122ab32848b23e7d84947dec71b7373de4940081f2aa21b09bbb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 27w5wAWSFjCW7MyjJ3hCAB4mY7R0sNN8LtmPQXDXNFa3gCkatnjHVYOuaTmCK/EXLyOb1IaamYY9RZe8EsqIDw==