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
- eb475c68f22c3ecc1b0c9e725a8c8d0463d325c92eb208a0408431a3607b4214
- request
- d2511603e1a4de0c2b1290dca6ef36e685ffe607718b4247fe526f76ad09e19a
- transaction
- 7a2f3b5d3bf5a7cd1f2826d856ff10153892615321022bd53cf603ac71fbbfe3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66623
the chainentry 66623
- sealed to the entry before
- 15f0310cf5d89f5e9a945febd632976e1c5818ef979fa86f3bb0442f25105492
- this leaf
- 690ea4dbfa5cfd061847d07b1b5be7713ab777ef6f7b472fdbf9e1661e847060
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y5iCrWM83mbul/8YLPrT1t0V4+2NAjwrV5QwV3kdISNgLn221XFT9I3rwiFYuNO2ZwoBtD1YL9IhUPutapaWAA==