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
- ee84186be2a8c61ed8cf824f36e237c43aa3c967956d521099725a3de1189a52
- request
- 4eaf3320de512d94ca14b2c1912c7e6490aea4d53bb6b00840b76b6f3a74bc5a
- transaction
- caa02cb33175b9736558aa091a69f256a20d62664a7004ce70bd7654798eae8acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63621
the chainentry 63621
- sealed to the entry before
- 862b755f5cfd45b89ee6dcba070951c63e30354261b19a873ed90b2670075088
- this leaf
- c59f78c4030fd589c7380420717cd18a108198eb4f9dc818c4504fc9b127c791
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r0cn98Xz1+b8gerJMsWvIFWFwvewlXbCbLZZJjBo5JthLokXFGe3AfPTy3iw28etY5fW+c6HieU45Z0T3ERnDA==