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
- c0bb2cb1f30e33c23fdc9e3b39359d10375a3fbb178a94a32651ab29ee16cd20
- request
- c8f172c037e0d6d6147c2bf6d71fc8f5177bc8c86afcaf3fa907da126d624100
- transaction
- a7843f17de77512bad84c84e6687ba6041ef6e99d5003ca0272950c502c1102ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14121
the chainentry 14121
- sealed to the entry before
- 50b81197300be38636ae954f77da5a29eac697625d15977c39353490196c5442
- this leaf
- 5471ca2b1065b678e963ff9715ab30251fa40c67ff37e681be6638f2a4de0794
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LTvrLcO4sOXmm9HQF0V3Kqnk7LQExHlrbuRAneSfOElIDMuYD4IbrD8ClJhyi8/2/cUoS3iYot+AVOpb4HilAQ==