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
- 7057c01d0a2003f76b66757d4e50348eff2871f320cb11eaf8c212049eef6424
- request
- 0ea0c8c131b8033730b3a74814bd87716597bd06043e7e94e0dfaa9b077f11f7
- transaction
- 7f5d9b8334b1962583c8e08bb6832193cdc2a1ce955245e7fe88f5ca75a77aa9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49966
the chainentry 49966
- sealed to the entry before
- 0ccd27f77d0f6b964eadcf32685c3784d1966f7ab3a9527b6e53ee0e14e006d3
- this leaf
- 9d8245f60b64fec7219ed7bcf4c6cac768c77bf9327859de2713dde01ea6f3a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E3mTy5r8zdY8wGiLtWji/slTZcTfjKRxSckKMDONEiq4OGvi4X1TrTqpqJfamaw4220DH7aKq2Xj7Ydl9XC4AA==