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
- 315f7641b351ecaa3d6486dcf6d3a68845b01be769c184b6f7ae657922b9170b
- request
- 0ad33ee32911f24fcf3de1de089173689c541f93b9e82acae276b9c99c71c2ac
- transaction
- a94404dbeea42d5ab391fde330927a5a27055a3e3afcff91a1ed693405e58b36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2400
the chainentry 2400
- sealed to the entry before
- 028c86ee6a3df13281857bbfe876b2f97e698f324473d05632ff6016982454a3
- this leaf
- 0f10349c54c6f0d8c9dd6553fcf8525c7ee98827ddd3e46abe2acd974a97a43f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nrHwkpt2T1g9D6g2eY4U97Dn2zT4G3lH6hQNbK/rE1Le78mB8nxKzNcvEyYNAtZfoXMfxXzqur949EsxqzgIBg==