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
- d05dd1ee5573e738132d43685563355f2a4f04301955f459a250ec0674ba4e4c
- request
- 9f8d3091ddd5814c9bdeff0ce608ca286186c41342a8d5333f7b2cc8123df489
- transaction
- 3d20782687380e4c43f58018ed2c7db60f1f640ce83e945a4e20c8a444221f2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26100
the chainentry 26100
- sealed to the entry before
- a5960fe657268e5a8b2240e79183f0c42f7177efa50bf268807b85783f3fd7c1
- this leaf
- f5da5186fcb13f3e2f2e251d2545851f28bfcb7c76fcbbdea1d2f8e66ee24d4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lPbiY0gM81xF/PQ9hkprgMzRkYJ0rIZvzXEos9nHQRyNpvTnjAK4QzpnYPfG6BctyDP/i+CtkWrFhe+LmpxJCw==