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
- 7dc2da1973d6cb9f6894cc4ab670a5dd8f8907143dbee2453a46ad7e45c12f79
- request
- 14f08f6aab8e5e647339b0f2692ed8a1b8bfa6940f1fd4c2dba2f3709a3789a3
- transaction
- f4537fc146525498b6250f21760c395acacdb453696df6a7ecd38a40b954883acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53336
the chainentry 53336
- sealed to the entry before
- f33cbe7c116876c8cbdc7b2dd397fb50dc1d9a7ba62100a9ca81ae4a5496d265
- this leaf
- 4658909677bb42325efefb25716e88a9280e3ea942492d605bc3df4b91a50065
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V/OIR3aICJseMK6xamPPvABaWSPK+JCzDv5J8UDsQC1ne9FcOXZj3ppRljGUOXzf/CzYivfqgGoet0+mztaEAQ==