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
- e65439d9618ac17a2586f43ad458c79691c30aa7d7bc825ef5cfd9797f3b5574
- request
- 50efecdb3acc2d5763471a47b7b4d5a5038cb2e0055ca8ce05baaa56599d8bd7
- transaction
- e1a3650a75ac291449029d4066920f62c29cfbc095f2bf2a6d66f44bb5893c73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39659
the chainentry 39659
- sealed to the entry before
- 5b48f9dcd5aa86f6ae604981f16227bff67adb6a0b6f893444fe0365f580f478
- this leaf
- fa3d32805c38a8c80fd48bccfdb0fe31d77e925ab9c95240c29e9a2fdbd77b53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D22+dZxFbS9YzV5QATx7iZzNfGZcEHoaOSVZQmoePkkiuRbAk57pm4SakcSCMd5n98kEqVZqKJQVtKdIFGHCAg==