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
- 271b3faad0557920492b2fe5d7fead676af00a91ba5902df07c2838a682ac9fd
- request
- cc22fa82037093a9a9defd626664fba389cd49c7d22af22be207bde806224b5a
- transaction
- 1254109467cb43411dfb4e17c011052a9fa2701c5a138847cce26be0802947b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75750
the chainentry 75750
- sealed to the entry before
- 21a894f7e1272b6ceb82f3a4b33340400998a8f7070cc31d573cee968b0fcd17
- this leaf
- 13f3c6c57acaa4c7ccc88b2df2b182d401de7e12dceb44aff845aa04575bade5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F/IV/nhMG4TvgVrRzbuPHQAWpeNU/cb9dgoCKjRdB3ZZOBNP8QWEmsQBUlNlr8tm/kSjUSX35MR8QZnY4J9cBw==