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
- 19fe2d33c6920f416f496ff9eda08ac9cdac4156efcdff02354a06a2b0472357
- request
- bc6920551abe3a3e04eea2662e0f96bac17f3e531c5a86248d2a63f522885443
- transaction
- 601e2a38e47d82a2c574b20daa0d7d1d81020ac721c986840576db26414c629bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4723
the chainentry 4723
- sealed to the entry before
- 33f80bc06254f03abad52e3aa4879099c23a553e62845a405c45d96150a010ad
- this leaf
- de608faffe3d3730ca5b705289623190b033c4940f96e36d13fdbcd0ee613d07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d/BEpTyx03982Vrbo5qmgJE89idvFxFvS9LsqB4NOkmOsk4uY52NkswARpEVDl43YkfIhgFBzPUSaF7Pw1YOBw==