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
- 4cc1228d042868f3d232ddad4484d3978000baa4aac6b65a4f3252a9a3ca9f40
- request
- a57188e09621ebc512779a74ecdb66de7249543f8fc194102e7d91f0d93af374
- transaction
- c24dd9824976afec4c64952bc53b0ca1ec8381a1c93ba0908dbe2e810f96c05dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3929
the chainentry 3929
- sealed to the entry before
- e462ddccc9a586076a0d81832a4b3306c71458fd9bca473cc414ad77c0977ced
- this leaf
- 6068dd1505ce3a3b1c893e731905c8cdccf255a6737342ebd4b480bdc1e1b762
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rF3kI1jN2LI4Sr7Xf8ILadyw4HxL1SsitI9UZd0EkRI8DhEV2WZfSdFohZRxHF5WLt1hmcpDj2FlLbYZ6UO8CQ==