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
- 5638c56cbaebed8d3798e59175bc62e4b7edd57af974005bbdf754abae7ffe88
- request
- ab8599ab38c4d46af3c17445c2aba295b5cb1152a9f52abe00380fda13bdfd21
- transaction
- 81abcb0bd9bb1d5bc5063ec42aa0e6d55408944ba401121ac2c51bcb57bc8b6dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63453
the chainentry 63453
- sealed to the entry before
- 3e80030652636c7162c5fc589ecfad7c1a5357355d2ca5e7a24ad991124eb241
- this leaf
- a88fbab94e8187a3e8a6bcc8e6412ab8ebbfc2d75a4351180f05d137d09bcb98
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jFcu1nD1o+0QAZfLzOsS3AllxKUe8l3wLVkelqVBd9PgxgEaRTxfzguIC4/3+rx6B4xYuyLTlQUnGdMEec31Cw==