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
- c8523f734ff7e144dcf7458e457256b6c5b0cfc9d89f49aa0c352e2c008a4fa7
- request
- e459b9c615b363602b4dea38d865c07f7c3075ccee62addb22053cddbeae1620
- transaction
- 60d4efa42b6e4f0058bd7eb4306d3d1d221205323d7fdcbd49e2b5ce6941b88fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40063
the chainentry 40063
- sealed to the entry before
- ea13310176a35b6cea7e4ef1680049de4660aba11bd752da223ff348b605bfba
- this leaf
- d1b4267fa1bd949e17555d85421e310aa86e6af53502cd217b4f2627bf8b8cde
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O4MGOvAolhLoFM8McscxErSo59MFiDM5eHi0dfgJOYjhjtIvLc5nIYoMzS6i5z2fQXHlSSdeX9CL1Klry/KzBw==