Here are some possible incorrect configurations in Eastnet's Payment Safe that could cause it to fail to translate MX messages:
- Incorrect MX translation service configuration: The Payment Safe system may not be configured to use the correct MX translation service.
- Incorrect MX translation service credentials: The Payment Safe system may not have the correct credentials to access the MX translation service.
- Incorrect MX message translation settings: The Payment Safe system may not be configured to translate MX messages correctly.
- Incorrect MX message translation mapping: The Payment Safe system may not have the correct mapping between MX message fields and the corresponding translation fields.
To check the Payment Safe system configuration, you can log into the Payment Safe administration console and navigate to the Configuration page. On this page, you can review the MX translation service configuration, credentials, and translation settings. You can also check the MX message translation mapping by navigating to the Message Types page and clicking on the MX message type.
If you find any incorrect configurations, you can update them accordingly. Once you have updated the configuration, restart the Payment Safe system and try translating the MX messages again.
Here are some additional tips for troubleshooting incorrect configurations in Eastnet's Payment Safe:
- Check the Payment Safe system logs: The Payment Safe system logs can provide valuable information about configuration errors and warnings.
- Review the Payment Safe documentation: The Payment Safe documentation provides detailed information about all of the configuration options.
- Contact Eastnet support: If you are unable to resolve the issue, contact Eastnet support for assistance.