In my opinion, logs have two basic functions: ) monitoring and diagnosing whether there are problems with the system or business ) troubleshooting . For monitoring, we need to know a few basic data: business/interface request volume, success volume, success rate, time spent, system return code, business return code, exception information, etc. For troubleshooting, we need to have input and output parameters, intermediate data processing context, error reporting context, etc. Then, based on the above analysis, we know that we should have several types of logs: Interface Summary Log . Track request volume, success, time spent, return code, etc.
interface. Using a fixed format, it is enough belgium email list to print basic information such as time, interface name, result (success/failure), return code, and time spent. Business Summary Log . basic business information, return codes, etc. Using a fixed format, you need to print: time, business type, previous status, current status, return code, basic business information (different businesses have different basic business information, such as inflow, payment amount/refund amount, card brand, card BIN, etc.). Detailed log. Used for troubleshooting, not for tracking. The format is not fixed.
It mainly includes time, interface, input parameters, output parameters, intermediate processing data input, exception stack information, etc. System exception log. Also used for tracking. The format is fixed. You need to print: time, error code, error message, stack information, etc. 6.9. Payment Security Basic Concerns for Payment Security Payment security is a large category, but generally we only need to focus on the following key points: ) Sensitive information is stored securely. Store sensitive personal and merchant/channel information securely. Sensitive personal information includes ID card information, text data, and payment card passwords, etc.