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
- 7cd0fa5eb932d86e75ed034a9b367dda3b75950b233d3505765d839d0cc13f56
- request
- 85be887063cd2c245dfc8153adcdeb8a1023bf5ce1b5be0053cd00c4209fc0fe
- transaction
- 7f6113fc025c9343174a432b6b86271044ba6f7303e1bd21a7683cf9d703fca8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72106
the chainentry 72106
- sealed to the entry before
- 8c036bc9ea1d39965189662e4a33bc5487b8c98e7e105d15e9d3135dfe10fa9b
- this leaf
- 87f51c71a68e774bb0571db52c221a0ee25e0781d26e60c69d7571df51e45830
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kntjDMvOMow/bHIXHnfOS9p5ew2pEjgGXGExNZGuAhbxNr3VClJ4+lafUpCqhcvUZFxloGG17z6DfFuUDTY4Bg==