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
- 54e1feaa11b18649ae3af4c310b56aa151a63c4682246b52775e4c90494f571a
- request
- ce12c1cecffcbef9e18789b806755abae630c06a023a1d61c4e9d1e79ac4ce69
- transaction
- 2db79bb5d51afe22b8d181d5620d21e5e8ec6127a7fc85dcb8cd8bf0efcbaf39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70807
the chainentry 70807
- sealed to the entry before
- 95b4451d8daf65943e26b87fa28eb544ef65a093c41c37e0144a1a4d8595cde8
- this leaf
- 9a477d32446db4d5a46f676eebadd47b9e56665c70aa31f7df7749dd312be174
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l+HqTDOH6lWrJC2DT3DHbGw3yMHND13YZ6gMTWGSL0sZHWf0t9lXSmsIYS7yyowE7DtK8390TG5jaIJgZ60OCQ==