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
- 41d7a59ba7d7897b31dea142c3623790843bea6cb90f55d4e6e3221a2d2b81d2
- request
- d2b52e61fb23d090cc309733251724b54668ecba12271ad64524e7c1a73eef46
- transaction
- f4059075b2cbd32b7f6c7f2ba0a3e110793154dce4fd9565cedbc95ffce8c5becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30118
the chainentry 30118
- sealed to the entry before
- 99e851639516cb11ee0f20f4276cb693772fb25dfc721381b2978b66b735b51b
- this leaf
- 0ae0c688ccf240fe988b4c5eb28387ec927cba296949d4ee100e84bec5388778
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vTKCAh+27CE/Wzm2jWvt14AZvxB2WmF3k/6CRnN3XVfvxwesOHnQJVgX1FEx5QCWuJJJsIYdgk7W9cCIAkdmAA==