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
- 64e72171ead5253b955b17833eb334d0b76d1f66e14fb3c26ea4c1befdf6a51f
- request
- c11efa0b9af57b574c7e6a58ef2611965712f612a36ed37d5f53c38bebc76a1a
- transaction
- 97b4833a8ca97809d4fb9bea41e1dd995ef69311a36eabfff1db813c684a07c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75562
the chainentry 75562
- sealed to the entry before
- f92394b37f51bca711de3185fd822a4a46eed7056f9cf801faf2879a33097eb4
- this leaf
- 6fb035eb83a4c6b76bca707cb46e16a2368f0a935d201fd6b4687d4da013b32f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X6EOrd+uT9gPzkKe/AqXUq80l/bPLH2pBAbS1w3fJXu8J8XfT57c2m4u4uko520cPDrnOp9FrAT5LBCNiIxSCQ==