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
- debc3086da5f4c8d3d8077611b474d7dcc4d9fa111d2546beefbcf162b471ad9
- request
- 1323d133dbd4de5d781549f9a27453f26eb7d9c20534d5e7ad0eb53d185573b0
- transaction
- bfcf09f735770599894abff60d2b465f81f0c0902bf9f9f162ead7f474cb9814computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75576
the chainentry 75576
- sealed to the entry before
- e2b36fd6d9713ef1247138c3f45cb3998ee289d5f6f0c15b5882fa28ea0d24f4
- this leaf
- 6a77c80814cd9d758e6d3f5c017005f6f1633dbe476e9d6f154d17c379939a96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B8+rmRuoGMopkTRTT3kvx0YHnEo/Kv1BYWEFdPSjgoIyd1V5p9Psmz7+KNDbpdIapMuHcObkUdMV0wH8ZlnGBQ==