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
- ed78f6e5f3304644e6900522e85b9bfb9f46bd40205278dcaf70b06d4f369e8c
- request
- e22f471d564d40260d95d9e9a15d77156e8f2d4f1509c9165e22fabc42d35e83
- transaction
- e72a2c8307873a767a85e6a62e3e67e306bcbed6a2bbd76cbd3a6a9138966060computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55380
the chainentry 55380
- sealed to the entry before
- bfafbcfdf4dc05aba2626853eb215606c0cb44313003c0e2bf003e284b3e973e
- this leaf
- bdc88929845a07d4557e99f4206c2f3e5ac937d2bac6b6dc7720e9ca15e1e2fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LkDWztsvXQH1qu4oRrg1IV319aD8Z9JqGChHSFrrkaiSurfcZJV7IKp1a6CWZzVK0TdZDnJHa24XyS4jrNEuBA==