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
- 64e7a6247057dc740f24870d707d4683f5b01b637cb1daf161879e65854aba8d
- request
- 500d31d075d10eeee460d2ddc03e9226ca09ed0a5414771fbb82a6673e3744d2
- transaction
- 14eb3d72a347ae088a24d80f8ba128aa3a01ae9dd61f12bb1e813fdc507f2255computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73088
the chainentry 73088
- sealed to the entry before
- cd3d90aece0ac6e212ca6afbb58fca89d99bb8f545991d2a654f7446ff825b7a
- this leaf
- 3e56d7a109afd59f7c76f8551d17cb177fd5c0ed194736c79617a0257f6e5e1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ohfUVsmu/0ZQ7XCvpTSJDpFvl5DrhEp1YL765bZngwUTvnPnAMTDMfnySN6D1NgCTKYZYevnWvLSogJyC4s8BQ==