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
- a9718409858c7538f7c0a0c6fa1aa118b8088313d419982fcc42f49d3bbd74a0
- request
- 2e06467874ce256ba21afdc4bad99ce388126d9bc5d2ed21cfc2fe1b6d08e574
- transaction
- e297f348dfd707044ba98dd63194b419f6658b353e01c1bff30aeb82c3d592dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56468
the chainentry 56468
- sealed to the entry before
- bd754d9f6d3b5b1fdbdbaa38494433ab7f4c357190d1cabebb591dcfc95243d8
- this leaf
- 2be332e11208214f08ae84f29d1c126fee4f21159d84a3ab4ca1795832a94b92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tMJEiFy5mxpomwSjucCajBw3YzYUw4sVhapqvruhALrX7QYDWKC1FvD30kLXZUsE0agWG0rlZV+vB3Y1tXP0AA==