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
- 838272e45460c452c971da203fa9a0ed30b5a9b3b40fef2d6775d9f8c2bc277e
- request
- 64f382f1b352a3e77dda7e9d138e7874056607d824e88eced070a1e64de3cc49
- transaction
- 22ca02cb4d5e82c611386de5620cad6c774c19b02757081dfe4dff275d36b525computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72033
the chainentry 72033
- sealed to the entry before
- 038b097f619702a184b0124601871b62ecf2e67c5c2c7920bf7e2e19b8562998
- this leaf
- fc11efc839074eaadab9c88cf55d1b11e94165dc41f4753d4e6768c4913e828c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kg2mb4VYmzTYNIfz2colQwrkeOfvAlwgIIT1YyAH4AzsuB4jqDXj88arJCFAaCjT+LExnch0kO81+DLMClsRCw==