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
- 11fc58c2a728930bd44d72053b05e613e4f8de626d812943e522e52976287b2c
- request
- b90521332e4cab9b12ce3cd236ddb2b578022771909861239d04813fdaad3dea
- transaction
- 068b175b3c5f50f98ed48e724ae01f3f9bf8065c880dedde9f4ad94dafc59690computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2265
the chainentry 2265
- sealed to the entry before
- 1dfb594e5fedac21728c6f5f39b194dc652345f070d2e81dc5ecc6163c54f8ce
- this leaf
- aec356b374d125c7e9e67dd0a526f67f311f6f8cbd2498a0c408d3bf2c11dc21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MuTwyUlxsF6ddUw0JdaCFZO0+7yb9b91ksWEMLKEUphblLEa7Qpi/vaYeJI2vWOWkI5zvZsxoZpcb+Fv0FfzBA==