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
- 24d56420eaec65e84768547984a6e8b28398a65f4515833a1abd7c0a3ddc8b6d
- request
- e4be7b56efa748e051bec23cf4418f43e68bd6ace7039ac3d7b4a513abb6c3d3
- transaction
- 1cc03af555bd7348556fdf8727f7fd06ebad6d5dce599d6f63bebcaad9bda2e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17223
the chainentry 17223
- sealed to the entry before
- 1bd60e60b11f2297566989bdd05d18503ee0f6546df728198078ececeacfd31f
- this leaf
- e503c5417747c19730109ae86f6bc5739329709314ada3a1c88161b690b20440
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TDO+NyrIYJj2bhckLNz7PfGsB7ptENtKQJj/Qb49rBUu03H6HVkT1x7VrNIjUUmvnVgPIj7CY09cZQeODSybCw==