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
- 2dfe7684fe23f8cdcf54153f831c3304b3fdbed8f77d5c630e3dced00e0e4e4d
- request
- ccd42bd5d6335579e3fd4ff056678b79405da4ec6effb01799ff785f77bef2e4
- transaction
- 135984baf041eaea3578317e25bece82f2df4ad15bd0591fd62b8df57e5fc31ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37661
the chainentry 37661
- sealed to the entry before
- c297660cddd94d52edacdd8f32b823ac4de440bd00375deabeb71fa2bd90f3c5
- this leaf
- a26cbf5c75e3a9257e45b83285e7988f9b262c3589bcbafed1e7dc01f0abb47e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bB/OFViNwT3BMcA64rCM3hO+0aoRh3uz/qGI4meHYjQ59IqaShsQP7spCoQ1ItHCPTHqGEzG6riLTdBrsJCGCQ==