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
- d3059a33af58fca98d34e4eb6cbfd1dec6865c5690eabb299b8cbe5a5086ac5c
- request
- 9b4fd51420ca95cf898b1f969db715689b85a1ce884f207b559396cd7b3a0ee6
- transaction
- e34367831f2e9ea0a9275ee132fa9c20e17721cd202abeaecd36373477d91b5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40456
the chainentry 40456
- sealed to the entry before
- 5831ca62131d9ed546fc92d4275263e2772064665c261a723947ec9e094b539f
- this leaf
- a360896fe5b0a65adb2c7a37562bb3dcf6c4d2443a4b790bc83fcf4dde0e987f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ax1XXhvSQ1AucJGmhZupq2hA454WSZcVg1DMj+q4WNZOOcVm+0cSLnGd6ri4B+HulgQWJcLHIlmNd5SBvK4mCA==