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
- 50bb7b164cf22c6d3bc0337e5a4ad6907e095a5ab9cb0f1e064e2a5ddb65ab4b
- request
- 01eec0839c00e620b33fb250d3f26cc5a616fd9faa5ffce4ecdbed189b9d93cc
- transaction
- bac95f905ad09e2eed319694f9794c7bcee0be5d0835cb0305eae2c6c3cd5979computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3022
the chainentry 3022
- sealed to the entry before
- 0d8dd419eaf04258ea19ceb4dc87c02a45164b45142fc3055b237bedbe934674
- this leaf
- 841e2ed32a91f92815ea6923429950699d024db940aada796a5039a1ebef19b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VBA0ig57crsQWcpSe1JubXJLqyMv70WAshuPoQoiSFszoHIvk9gX6fxcQbXAjd1najMRYeUGoMfeDdC9YXIbAQ==