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
- 505f4245b179ec54decc37557696413c46232f8737787070ea4df423fdf02dbc
- request
- 75be8ce1287516997d035a227853a6559d27f5f111a1f61017f38969a5db1dd9
- transaction
- 50775a23a8b1e3aff1cd136aa373d7ccd0ec5bca9edb3392a0b6290fac650c8dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5316
the chainentry 5316
- sealed to the entry before
- 4c07c539b5d98fc6ad1d05efd57c2c0c1518f8ca05d448e386d3ee81a355bd19
- this leaf
- 30d56350e5a132e0ee1560b9e65e1e41c2a04ef2649063b17cadddb8d1f3dcda
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MntKW0snBVt9ENbtedZKPk5WzsmTCyppSI9eqAsRmXthy1hpdldEIyx194qe/fTGq0t++jxeF6JhsLeJoZ+lCA==