Frequently asked questions

Below you will find answers to the most frequently asked questions about the connection and use of PunchCommerce. In addition to step-by-step instructions, you will also find background information on the individual functions and technical requirements.

How can I connect PunchCommerce with Coupa?

Short answer: There is no dedicated PunchCommerce guide for Coupa, but based on our experience with other customers, the connection works by setting up an external supplier and a PunchOut connection.

Background: Coupa supports the cXML PunchOut standard. PunchCommerce can be configured as a "gateway" system that communicates with Coupa via cXML commands. The connection is based on a clear authentication (buyer/supplier identity + shared secret) and a defined PunchOut URL.

Steps:

1. In PunchCommerce

   • Create a customer (type: Gateway, protocol: cXML)
   • Assignment of Buyer Identity, Supplier Identity and Shared Secret

2. In Coupa

   • Create supplier with "PunchOut Enabled"

   • Set up PunchOut catalogue connection with the following data:

     • PunchOut URL: https://www.punchcommerce.de/gateway/v3/authenticate Buyer Identity, Supplier Identity, Shared Secret as assigned in PunchCommerce (domain information is irrelevant) Protocol: cXML

Testing: After the setup, the PunchOut should work as usual.

Additional resource: Coupa documentation on PunchOuts

Why do I get the error message "Unfortunately something went wrong" after logging in?

Possible cause: The transferred Session ID (sID) is invalid or expired. PunchCommerce checks this ID to prevent unauthorised access.

Solution: To test, use the "Log in as customer " function under Test PunchOut catalogue in the Step 2: Transfer to your customer tab.

Background: The session ID is a temporary security key. It must be transferred exactly as it was created by the system.

Why is my customer having problems entering their access data?

Checklist:

• Check whether the user name and password are correct.
• Ensure that the USERNAME and PASSWORD fields are stored as fixed values in SAP.

Background: With SAP OCI connections in particular, it can happen that variables or placeholders are transferred instead of fixed values. However, PunchCommerce expects unique and correct values for authentication.

Problems with the integration of a catalogue for the OCI-PunchOut

Symptom: The catalogue cannot be loaded in the iFrame in SAP.

Cause: The server sets the HTTP header X-Frame-Options, which prevents the page from being embedded.

Solution:

• Remove the X-Frame-Options header or
• Use a subdomain (e.g. punchout.shop.example.com) and remove the header only there, if necessary with nginx reverse proxy.

Background: SAP always embeds OCI-PunchOut catalogues in an iFrame. If this is blocked by security headers, the catalogue cannot be displayed.

More about X-Frame-Options: MDN documentation

Does PunchCommerce support both OCI and cXML PunchOut?

Yes, PunchCommerce supports both standards and can therefore be connected to a variety of purchasing systems.

Can I create multiple PunchOut connections for the same customer?

Yes, this is possible. This is particularly useful if the customer uses several systems or different test and production environments.

How can I test PunchCommerce connections without using the customer's system?

PunchCommerce offers a PunchOut test function in the admin area, with which both OCI and cXML connections can be simulated.

How long are session IDs valid?

By default, session IDs are valid for a limited time (usually a few minutes). Longer validity periods can be configured on request.

What to do if the customer only sees a blank page when punching out?

This can have several causes:

• Missing or incorrect authentication
• Blocked content (e.g. by firewall or content security policy)
• Expired session ID
• Incorrect PunchOut URL in the customer system

The PunchCommerce logs usually provide information about the exact error. Please contact our support via the ticket system within your account to view them.