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
- e231b78d10c55fa74e19958728684970f9b9b80cf6c570027ad18950c8dadc37
- request
- 4cca20382b1a77cd6e66d164be2fe8f42d9f5d07e4d0cbeeef13a25bb0283de0
- transaction
- e936658b60ee510a7928970aa3e2b1c0118d13fc9f5d00adbf4e426391ecb2eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3204
the chainentry 3204
- sealed to the entry before
- e17aab6ba6dbfa16561885455906ef8952f1885cf71e46d6c2b5b3258fab1bf0
- this leaf
- 0e97147da2582594c6e43cdecf4a0f3b778d35d7a46eb6eaac68bcfefa0df1b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R4YPXauDpyLcyQIXPwthOAz6kcG0kdEDAGQytVgqoZ1rWrRiinzTcHuN1tGMvjrCK7Brcrl5rSPZuy/VIuZjCw==