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
- ae7321b26f82198b6d8a927c9d2efd3256ebfb3ae56e6931ea053265dbbe1c95
- request
- c264b4c40ec46b40f86bd0f60c42787065ebb513dbac21828b273c4a2e158849
- transaction
- 130b53145f63f878ae0aa0fa4b3ea9fc5ae27ce75c7bab76415693d1c7c05926computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44839
the chainentry 44839
- sealed to the entry before
- 8491d2f8af4392e73085938da526dece28952d736bac413fa4bc711eecfa90fd
- this leaf
- 8a312fcb8417e6ae4ec3d672acd3bfbc08f0f1eb45141cde11729dc4cd8f5b72
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8JJTWQi/TRLL7bgq3rTN7kCTKL1tUrKbt1eMwq1Cz9n9oZn+jABZ+FU2+2RtBIJxA+jINaQrHiIcQb2U47+JDg==