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
- c240930fd9ccc58145b45d6f693e31e6e276ad5182bf52adaa94534764896d34
- request
- f01c263b9c1673b29fe74dd28dd8fba17929f6640354e824fabe1549b04d90fc
- transaction
- 3ef8c853292f5768e815155f4e0008e876325d8efedfe0c758fbd3c28783612fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1490
the chainentry 1490
- sealed to the entry before
- 6effd06370e8b22b388634a515d8f994a9fedf91e0348dad83b789f3cd3156cf
- this leaf
- 69e478a393c7067d3a490e25c422e3d02307bab935c3e8a100d15aa74240035a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nsMX6z11Ho/5upVJwtmzHTV3Zh4NZKttIfQv8q+lkSdGHWVMp5Dd+qZpM3EVbvqPcB9I92+rlFIaqCnb3AJVAQ==