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
- 9bd5ef8da849291abade729c59a944446bc766291a1e41e76202215e0941e694
- request
- e607afbf2d9a6b9088341f3efac1f52c6c13d072fce42989dd66ec156009b231
- transaction
- d5e1793df3297559454786050276114131f4462d36ca34e3cdd6ae2bc802799acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28609
the chainentry 28609
- sealed to the entry before
- 3fd5377910853b8ac7034e2bb570bfb91b4b64f5f035797f4e08edd332a17c4f
- this leaf
- 262836e2636779a7957e0033b4c8eee7093667bea52486000b247dba054c0897
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XCvCmqalYFEnq8382uDzGgByg1kcDGG4SKV6T6OvnnJoe1SZKnuXAu4HPPswBwLNVXFVgWGicgwfmVLm9i1PCA==