Error Message Masking
This feature allows platform operators to enable "Error Message Masking" for merchants, replacing detailed technical error messages generated by the system with unified customized messages to enhance information security on the merchant side.
Use Case
When a payment transaction encounters an error, the system generates detailed error messages. To prevent sensitive information from being exposed, the platform can choose to enable this feature, replacing original error messages with unified masked messages.
How to Enable This Feature
- Log in to the backstage management system
- Go to Merchant Management > Merchant List
- Find the target merchant and click Edit
- On the merchant settings page, find the Mask Upstream Errors option
- Enable the toggle and save the settings
Impact on Merchants
After enabling this feature, merchants will see masked error messages in the following scenarios:
1. API Response
When a merchant initiates a transaction request via API and an error occurs, the API response will display a unified masked message instead of the original technical error details.
Before Masking (Example):
{
"code": "9999",
"message": "Channel timeout: connection refused to upstream server"
}
After Masking:
{
"code": "9999",
"message": "Transaction cannot be processed at the moment. Please try again later."
}
2. Merchant Backstage
When a merchant logs into their backstage to view order details, the error message field will display the masked message, hiding the original technical error content.
| Field | Before Masking | After Masking |
|---|---|---|
| Failure Reason | Channel response: insufficient balance | Transaction cannot be processed at the moment. Please try again later. |
Notes
- ⚠️ Only affects merchant-side display: Platform administrators can still view the complete original error messages in the backstage
- ⚠️ Takes effect immediately: After enabling or disabling the setting, it immediately applies to new transactions
- ⚠️ Historical messages unchanged: Error messages in existing historical orders will not be modified
FAQ
Q: After enabling masking, how can merchants troubleshoot issues?
Merchants can contact platform customer support, and platform staff can view the original error messages to assist with troubleshooting.
Q: Can the masked message content be customized?
Currently, the masked message is a system default. Please contact technical support for customization.
Q: Does this setting affect transaction success rates?
This feature only affects how error messages are displayed and does not affect the transaction processing flow or success rates.