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
- 18f2fefdbec66f5da890a973c11b632a53ab0ca261dcca4fabeaba7bae55e031
- request
- 8b41704d576555b8dc2926ef9b286fba73f56af64a44928c93c0fa10f5881120
- transaction
- 9c1bc5785a3ccca5e98dd5ffcf660219518fc80c9fb7f5ea201ed25b6431a414computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75591
the chainentry 75591
- sealed to the entry before
- 36dd191278458696e26e750861bf6900dd8f12d63deee1c7d0630d5e0633f6d9
- this leaf
- 072cdec0ab8bbe8e1407aa35e0481f095ac983281aaa7196a76287b0ff56da83
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 753xZL6FP9eecC5awxt7tMGUFoFiJuWVIFqnbJUEEQqPuuLg5RCjjZfU0hFyHcaFGOvdVTo2IR/97v+7Z2voCw==