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
- 166bfb9f85c0f3fe7ade07f0fba33b6c3fff693c3cb1f9af5b66028683e0044f
- request
- baf296f4eaa4e21a8f5716ba77be2de8bb263f133e9239d51136da69832842ba
- transaction
- 64418a60b911bfed8c9ad241e998e1672721729ecfcd8d19ede3d48e22e7970ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26646
the chainentry 26646
- sealed to the entry before
- 08e23d48486671cb476de50ebf317d32bcc02805021e316074479b36cc39e675
- this leaf
- b1af365664118619451f91881c3902ed88d6d75c277f3cd12e830ffbae195113
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DUiK8PseptHQvL1D+qrF4x4oxHUSiE3kdihAZPGh6kPk4V58ykwZSHhRkH0xyzVQSMPFTfBr3IuIO9krO1FrDA==