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
- 08866fd44f0889a07cc69bf74184f0e640ac97729cc1ed20eb3c98cefad229b0
- request
- 43e93f37e86bd82d43393c6f3d38a0702871240aec99433af61e64762d9f972b
- transaction
- d4091c36129cf767c715a0bd14d2632df3c9c8d283e8eefdf295b5be002c7cf3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8170
the chainentry 8170
- sealed to the entry before
- 3ec3cdfb2068e87738fe929f98a8a552a5cf9faadf176619323ce42d9ea8f6a5
- this leaf
- 99af1f94e70bb210136002f408c88d2f14c34687065d70c105868ae8c5012a9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R8au4pnqQ31/go5xLWyus4XikoElAgfROqZ9vF/75ExOCY4ysTMOBNgNQndB/5XKemhkQOJH87rE9PlcURt6Ag==