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
- b049c1fc1ff32b799d4ca29ce038c24e19b57ee84d9d046518b72a14d893dbac
- request
- bb56147aaaa410119242063c879d003cffaa756ed6cf7f78b2b5f2589caed9fa
- transaction
- 5289fe2cefbced25502f4ff1049ffb055aeef9f136960b0cc5419ca695a0f9a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17052
the chainentry 17052
- sealed to the entry before
- fc55e15ea79c4e6f24acc9e47d3a661c15df24e88f1ce509e4ef2225a871d175
- this leaf
- dd4e46dd8c2e39ce70c7b8d76caaa8a75e07351fb54100b70ea8bd899d22cd77
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DRqiguC1GoRELHgyU5Mx/BhPlLeAIqplZJe6K7lQak5ScFJiBbN4JQ/R11+yIEfGP6Vi5BdceZYZw15onfPGBQ==