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
- 06f9ea59e75a5f5dfd493cc86dabaaf14b471eadde961dec2ac6b278e61a8e51
- request
- 24b9f4a98de131a2add927140ea36b0777b1bec812abb4f916e4930bf3a01258
- transaction
- 09438a5e85584645e64ee3e16b64d2d82181c4539c30b29cbfea18201313cdc4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1295
the chainentry 1295
- sealed to the entry before
- bad62dfbfc2c1b1654db804e0d8dd51e9e5e0da6e35e02320ae3bbee529cfb6e
- this leaf
- 2eb6f0e9a77659b736c1124873ec4bfde508102d74fad2a0db4caf8c28ca9342
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5/F71Jr08VoL7+VQ3CWSTKepg4btyDS9NROv1VQKg0dTCJ7ESnkfzV8gzGDtLxZ/F0F8NMaBWl+6DxMYHjgJBA==