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
- 425eadf05274444b3c99b88622ef9bc94a06be4d3e7516cabef34cd5a8f6ed41
- request
- 3af5e20477ffb6517b4b5b83a882f3b4798dcbeace6b093a276fc43620b6b2e9
- transaction
- f3902c9f7f90aaf21449fed1fa8ee062a6f2e03d5af60cd3eced270229d76b39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68002
the chainentry 68002
- sealed to the entry before
- de734c4df1df89d4a899bf10e3dd8352c4e648ac10a8c73c31a707db2d01f76e
- this leaf
- acb00c0fcee3d19de576527ed3b690090a3f169382921c42c441f6bd49fe4b29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UGNS67DpJuUGJgkLaoeWDRfazwYY4xpJ/1YQhYLr4yUF8xksmdGgiKgGGr0QVvdz6Q0lltSE8NiYaw3Mfu60BA==