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
- cb44437c7d08303e44c8d473abe1f4ae06adab915676ca33e863eb991dacf484
- request
- 37fac352d05829119c903027ba7fd6de8ab4aade643c883fb92635ffc985b4ab
- transaction
- ea870c11eae2b65297882549284aa96fe89410a812f34bd68d2aabd3e9c0a381computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14356
the chainentry 14356
- sealed to the entry before
- ceafd1fe033377bc9dc65a826c62c8da1789f6eac7ed9fc0f6d2f47c3dce3683
- this leaf
- f10e923cdce9f1c3c2182ed65c8e459bf4ca178bfe55e3f26f4f214dca9d84bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hN2qGAz/x35ZJKua7+D/SwB0OFG/bn4slBr2dMEOnwHcWBHJFPP+hDGSw1KH6VR9reD3q4dA2eGn2lH/kNftBQ==