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
- dcd1d2572b13f6769f6db39d2ff4f63f1f07031cf347606b399466f047a585da
- request
- 4d2633666c1984e36ecc8ef183a5b9ebd358e265e6e78f81260f9bdfb9a5c462
- transaction
- d3da1eda0720f9c0da6a98ac7f951b2d9244cdd7941f118aa60677b7b222a29fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69636
the chainentry 69636
- sealed to the entry before
- 906546bfbe05a879dc75899666192adb47701ef1a29a2750c675c8200cb40506
- this leaf
- 1e4f82bfdff176163e09478d8160e9938bcca0795ffe62507feed501451d385c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ptvzrIP9s31IBKCvHtSKVJx8hwdC+zwtjxJgdgkITLI7FOYuo7RUaHqYXvCZdgU2OvRfLm0mH3plKpcTU8/QAw==