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
- 31b1aee34f24f65382bae9db2e1243d65f764cb77b0504a636cb9de4532a6b23
- request
- 530d07fc9c9904b3e863df565dcd4b6c9e7c06bed06f958673a4cfb84a6ba332
- transaction
- fc2dba89e1349d2c9f67c7ea665da5679b95a0cd3ad478acd77851db99370710computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25567
the chainentry 25567
- sealed to the entry before
- 3a2c71c9ca470b450b070ab10cdc0ddbd325bed6223a6b992b60d6b75bff5a9b
- this leaf
- 44a9e7e981dbb71e0f634ee00ea62c52d57b01918015e89d48ace11e2e4cd9a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1cxta9KQSb1bt3NJRdGxLLo14G5nkpXqYq0wBSE7jQEJ8vrt988h3D9kHxrxi58qIskLveb5ZGU9EcGkiJQSBQ==