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
- 0dae1d9d204d72a1f1051f7ef3aa9e5f2c6d131b4aa9c588eeeccb69804b5c6d
- request
- 01b6e391b7e5fd6e892b641d3a9daf3c0446c6a44ba91c55abe27f953aa0b133
- transaction
- fbfeca96b2669ab0dddf55a98fdbdfc274629abd0064887d7717bb0f9eac386ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32837
the chainentry 32837
- sealed to the entry before
- bb297cb39252fdba05b96e408ccb4897a473a95a28aab9d1cb4a1f8903ec358b
- this leaf
- f6880c16d3cc22233445e66234ee34d0eba2ad48b8ef8d7bd5b354444a71411b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +VWmKmqoxvR7veapcaomAl3oStL2hoiKDh9ZQJnpNgrdtPEaGvHgIYYj/ECEG9u4Luy7DLFhC99iRcBVMyW4DQ==