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
- a4f168be0e771de6797b5e5e5c4f9a7462f3fbacbb8de0acd918fc8e448c0d61
- request
- a0431b12c186b246118d00e632d3c28c1aa53d3082c9762f8ceca3a34d4fa899
- transaction
- 58dc5b296d3f733108b6e5ba01c22fddc12231e7a593cc5cfb3381d9e945497dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59140
the chainentry 59140
- sealed to the entry before
- 3c4372cf04b04a3c7d46dd749d4263f8820a42b3c7082c81cc1f379eb92f479c
- this leaf
- ac61a9ca549a6384ffb7288434d8c88838ec6dbc1aea44f8df2c50488351e281
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SqGlTt7ZE/Tb4EJjH07EqzRXkW4WH2WECfhH2gj7g+Y1grh15eUCROGXkipDrhMXvAsHw14EFaMSKmIZgqJdCg==