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
- 65106fdbff44beb6d44e527fed4fb458b15a0113b54213b6897e677eec6aef14
- request
- a861d88150b67a28159bf2f8e2206fac28aa0b3c6d2a6a5b08af4efd16465c2e
- transaction
- 1072c6c90106bb5c12dbf569f9e68faaac0b12fd39bba342c99c6355a7e08532computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77729
the chainentry 77729
- sealed to the entry before
- b0d518be428f033531e8a42da974fd2c1c3f9dbd1e5f24fa59b36e3d62cdbe34
- this leaf
- 6279fce7bc48ca46a857921a60973d8ff2a57e548d4ffe3e90be4b07946525b1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GtuAzcScPBXkZ7bHEUUXGSQQhXK9jqo/0iEwQ0QnLC+RxtW/A1otHJd8T2Pm2kYnXbyzzzLvucSxO4PJrBYSAQ==