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
- 47ccca40547e0184fc8bedda8d15f753ed7ee6e6b8601b4e6c00fe58048a8fc7
- request
- 10570a18149f78b2ff14603e8e01f6e6c5911cbcdf7aecac59c5694bb037dd03
- transaction
- accca39b630f3d6a8adbc9b23b572b684af1acfb4b2a210593fe7476e87de64fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71330
the chainentry 71330
- sealed to the entry before
- 9c85a181fe105f2ea0942fc6177a5df68d5d44b388980a21c9b33b0debb94cea
- this leaf
- 20f3e06b5134c0b57af63671bfb9c04d99ee032646f957bf91e4e6cd1f3ef5d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aQGBd4wI6h6wVNnDdZgp7CskdVmtE+NdAhNS3GW6j/jOueG0JJ/WLacdaQuAkUUmgOf/iHZXOMDq0wi31PuZDg==