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
- ba8b500d46691eac2ff053ec70891b05d5cffa31f318ca06d97139b9d9fe266c
- request
- 7af015340ad8073ce9c3ce6edf8242628e033da8600eaa7bb6a77e5c6958d367
- transaction
- 1ae9c93e9d60caceaf832e626dfd0019aa5cfea90a2351da1a43ee791898ce3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36820
the chainentry 36820
- sealed to the entry before
- 4dcb654c158df1452ddea405ca0c7a52fda29753f2b2d5e19432c9bcb3c0f402
- this leaf
- 1612108c202e7a695ecd1d7ded99850d2001ec0eacb4eace971ff0a250e1b845
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- swOZX2LlqAotRKY/3rvknGmSQL1Vv5ytNLfbHzL+cWSoxepHibIT58Fv08dkEYb/CuFn0ljVxNkerXlc8wsaCQ==