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
- 6f76e35e303adb7c1a935195ad7b44e7188d368b625c69d89caf2dd9fcbfc7e5
- request
- 99e9ab109fa754b3c93853278fa4bf5bf144fec678ab84221b80619149e583af
- transaction
- 22a5fd2eda883cee036d30aa3b4252c0e4e677c84383dfbb0bf24133438a20b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11971
the chainentry 11971
- sealed to the entry before
- 1ec06420f38bba03233c708e8f841453788efe7c96cffc765c38277f4916897a
- this leaf
- 27c04226cdb0ae9ebe89285fd13db4a1ae0e503bcd1f30241fc54d40930e9fbb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rL1P3jmP0L5u4bTSWcX6k1oWjFB9OilUFk5DeIoQerm6wUvrP1cXkEUOJpyl6RivVViFe3yHhpB0m3SeHiEACg==