How To Fix DP_SHARED258 - No merchant alias found for PSP &1 and merchant Id &2

SAP Error Message - Details

• Message type: E = Error

• Message class: DP_SHARED - SAP digital payments add-on shared error messages

• Message number: 258

• Message text: No merchant alias found for PSP &1 and merchant Id &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message DP_SHARED258 - No merchant alias found for PSP &1 and merchant Id &2 ?

  The SAP error message DP_SHARED258 indicates that there is no merchant alias found for the specified Payment Service Provider (PSP) and merchant ID. This error typically occurs in the context of payment processing within SAP systems, particularly when integrating with external payment service providers.
  Cause:
  
  Missing Merchant Alias: The most common cause of this error is that the merchant alias has not been configured in the system for the specified PSP and merchant ID.
  Incorrect Configuration: There may be a misconfiguration in the payment settings, such as an incorrect PSP or merchant ID being used.
  Data Synchronization Issues: If the merchant alias was recently added or modified, there may be a delay in synchronization between systems.
  Access Rights: The user or process attempting to access the merchant alias may not have the necessary permissions.
  
  Solution:
  
  
  Check Merchant Alias Configuration:
  
  Go to the configuration settings for the payment service provider in your SAP system.
  Verify that the merchant alias is correctly set up for the specified PSP and merchant ID.
  If it is missing, create a new merchant alias with the correct details.
  
  
  
  Verify PSP and Merchant ID:
  
  Ensure that the PSP and merchant ID being used in the transaction are correct.
  Cross-check with the documentation or settings provided by the payment service provider.
  
  
  
  Data Synchronization:
  
  If changes were made recently, ensure that the system has been updated and that all necessary data has been synchronized.
  You may need to restart certain services or processes to refresh the data.
  
  
  
  Check User Permissions:
  
  Ensure that the user or process has the necessary permissions to access the merchant alias.
  Review user roles and authorizations related to payment processing.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation or the documentation provided by the payment service provider for specific configuration steps and troubleshooting tips.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or the support team of the payment service provider for further assistance.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Payment Service Provider Documentation: Review the integration documentation provided by the PSP for any specific requirements or configurations needed.
  Transaction Logs: Look into transaction logs for more detailed error messages or context that may help in diagnosing the issue.
  
  By following these steps, you should be able to identify and resolve the cause of the DP_SHARED258 error in your SAP system.