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
- 6624ff1fd2a8fd43b004f446df137197f7261c438f66662434a07f6ec00f2f78
- request
- a6963e7408597a60be71b3a95e1314354327ab9c41def17a96cd5cb6dcc39e91
- transaction
- b85d2bb60ca03f9ffb89836c86cf28e6cd15803ce1a257129c2108fccfbdac38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49228
the chainentry 49228
- sealed to the entry before
- 3581a27f1c43c0bcf5cb8aa56a080d52922ebff128fe8487c4b1084fdd461f81
- this leaf
- 05edea0382122cf54364f82a45ac622f0364b794a25e56650b937ec3bf56b6de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RpdPFq0fjHjBfAhfcxAqUWTp8oqWeY+Ob9J8maaW2TY+Y1erhYa4dq9a/vRK8KMoBKpo0OKn0EbbV9zbUvWnCA==