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
- 9a5ad138bbe9ac328a40a486856f9e9e7e3c1f746e67649d0e31cf27bbb8996c
- request
- 3804ca55f175ee67b1f16cc3dca5f7db027d2b6bb74028276c3c7ff3754cb130
- transaction
- c41126d326041201bd1f3e4ef0366ae6b9720558026a79c65afee50af05aaa4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43940
the chainentry 43940
- sealed to the entry before
- ea5dda85678211bcda24c029192180ff9436cdbccf72c3969b6785e933572750
- this leaf
- d73005562ea51c84476ffe66d8e5df2232889b2185f22167c67e9b1525801ef4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D2FwAQSwwjWR7wGI3fyPwRa+OWlvFHmbyJOkCKhBiBFsYBHzISCNQTeTrOGLkr3E9IMCz8SpE5dVFI52qGDIAQ==