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
- 07dc95ea8dddd16fbaf087863131dbbeb3568382702c5c148a3b9bb05f5e3cdb
- request
- 5a3bd9c2425e3994099f4a45e6c46a06b12c00531a2bf09e262d3202e450002e
- transaction
- 223b17ba7646f85cb2fef34532f754a85692e139ab99fa21828b92dba6441334computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66203
the chainentry 66203
- sealed to the entry before
- 364d85df10df0e1f3e323fe3816ae5326fcc5bab9861ab5568f4403baccab382
- this leaf
- e30deec47f7f8006e5e74c0192ab2c6de053e6348f7bc39869817ae552348a43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kd1vLLgijWGSnVlSO28IjyMucDYctPUcO2cDOb7wWsncof2r8OoKg6v2zNmnR6O8AHajgSnh123vNAE7Vyv2Dg==