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
- bd0e55846a3299e5a6ab0348c223c92ac85ac4f7505fc7f45876e2bbb89cf52e
- request
- 2bd224e883db6482e8b91961f5a064bdd1dc16d3c38fe965be08f5674d079228
- transaction
- 003a10713e52e48482d7373565e888ed15ab3579538a107f16cea47cfdd91c44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49117
the chainentry 49117
- sealed to the entry before
- cd37541a8e6236862ed13163c43f45f67c888be088a875ec9b82fa98babeb3ec
- this leaf
- c884a5d26af6548ad11465201fc0b310517d818559e70c911e8d3779e09e5935
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6KMo6gBFnSMy0gRf44B1XXDYiYj4925P2m6d/na7YlI+/Z4KVg+ea/6rqU6t6U6K+qYHOyoxyi+0e+BlB86JDA==