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
- 76feb25afccd6ff471a750f89808f5af56470e42a3fa2e29c42e2c79ac82a034
- request
- 2674f1dcecd72852248dfbc9bd99b29b16fd82a211084910f1ec6210e1b2de52
- transaction
- 4aad105b0d38c8d043c968eb16da34bc185553a7c0c230c49d7ea92b24800a58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52898
the chainentry 52898
- sealed to the entry before
- c2f76eefa5aa76500a70126bac2a65dc28e662abf4c40decb25eb551418fa4ac
- this leaf
- ce32f893f824ebf645b8ef27589fca3ff58e4d325da629a8bf609b0fa0099740
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PpzGLSzA3qhY1hN4xeGBSqu0e4cOpy9DgZcPjWdyi+FUbvIvajwm31+WF/t9qgqOegHgZRBXiOY4mlzBvmLIDQ==