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
- 657098ca754fe3d954db6734cc25c55c7ffbdd0aaf21b6e590dd0490c28df436
- request
- 71b957d239929f0e4d78983a1cf77d159a7ece26325bcfbf70e1dd63205e7e80
- transaction
- 9e97d3068eaab7b972ef44fe73029f2bc29278d9ed57d15bdd65139cb881282bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41103
the chainentry 41103
- sealed to the entry before
- 585fff9377203e5f27278a62237d91ae2c7731eda2d6aea4bd32fd02103ef2ad
- this leaf
- 2700dc080665ee3ae2423b6ae06cb40aa4419385822064910edc960d5c494779
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T0FPL/iWu2WVwDs/1wv2yU0eE5idEK22WNCWC0+PeIGe+20eHdH3IJ0/eM1R2sDNVw2QeFmbXHRVgho4y/dpAQ==