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
- 35d6c97d93204a46a08eb5d0b3cdd38891442a9dcca7c88db0f0550169f8bf34
- request
- 363daf167a5150b8df5e2aeab34224f85c49bb754f56016780b99059ca09183e
- transaction
- b95262319470172c2197ec21051d3e0276ce25d66f539fe733db20a1fa8d5c6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31895
the chainentry 31895
- sealed to the entry before
- d432e0175d54f59395f05d402fc12b8485b961f59a6978686f2cba2e1d546df3
- this leaf
- 979256b0174cb70ba1f8c3e0384b659f8de4fe8df85820bef29877d9ef3864dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4DXPzJoe08U8WeNENdI2Y6/w5e3c5WYaIUXBovNSgotdmX1fNkxZt2eV+xtB+9kwmtBPva6uWNRleG0XlUPcAQ==