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
- ee344e56b7d30827ef7dce88fe615a932db20a9372a8ed0382375faa9d9754a2
- request
- e00653957dd7d7d44349c4108473110b16496fe14459d35bf33a65e291f89b93
- transaction
- 74cffc508e8ec96665719708c8a74407b4a5119c2506be0f47c40774722af417computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67548
the chainentry 67548
- sealed to the entry before
- b25a8cf828e77dfbc31786a7924c18d82a4c11856bc4f7ac45c087ad2b1a4501
- this leaf
- e3dc2c107c7cdb054e0c4251f5e2c14bd996d02df140ada0c8e26d77e22d04d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XjgExRaV7E3ftwjJwfj7cI5YmEHNMHoss8XwK27/uy7e70lh2/WPq2p5SvBtlMh78LLRVDnHvYy7yzehuAVKCQ==