How To Fix DP_SHARED158 - Either card token or payment service provider has to be supplied

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 158

• Message text: Either card token or payment service provider has to be supplied

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_SHARED158 - Either card token or payment service provider has to be supplied ?

  The SAP error message DP_SHARED158 indicates that either a card token or a payment service provider (PSP) must be supplied for a payment transaction. This error typically occurs in the context of payment processing within SAP systems, particularly when dealing with payment card transactions.
  Cause:
  
  Missing Card Token: The system expects a card token (a secure representation of a card number) to be provided for processing the payment. If this token is not supplied, the error will occur.
  Missing Payment Service Provider: If the payment service provider is not specified, the system cannot determine how to process the payment.
  Configuration Issues: There may be issues with the configuration of the payment processing module in SAP, such as incorrect settings for payment service providers or tokenization services.
  Integration Issues: If the integration with the payment service provider is not set up correctly, it may lead to this error.
  
  Solution:
  
  Provide Card Token: Ensure that a valid card token is being passed to the payment processing function. This token should be generated securely and should represent the customer's payment card.
  Specify Payment Service Provider: Make sure that the payment service provider is specified in the transaction request. This could involve checking the configuration settings in the SAP system to ensure that the correct PSP is selected.
  Check Configuration: Review the configuration settings for payment processing in SAP. Ensure that all necessary parameters for the payment service provider and tokenization are correctly set up.
  Review Integration: If you are using an external payment service provider, verify that the integration is functioning correctly. This may involve checking API keys, endpoints, and any other integration settings.
  Consult Documentation: Refer to the SAP documentation or the documentation of the payment service provider for specific requirements regarding card tokens and PSP configurations.
  
  Related Information:
  
  SAP Payment Processing: Familiarize yourself with how SAP handles payment processing, including the use of card tokens and payment service providers.
  Tokenization: Understand the concept of tokenization in payment processing, which helps in securely handling sensitive card information.
  SAP Notes and Support: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Testing: If changes are made, conduct thorough testing to ensure that the payment processing works as expected without triggering the error.
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support or consult with a technical expert familiar with your specific SAP implementation.