This document provides important product information, including version information and dependencies. It also outlines the basic setup and configuration steps.

1.1 References

• Guide - Setup Concardis Service Connector 2
• Concept - Payment Framework
• Cookbook - Payment
• Concept - Intershop Reference Payment Services
• Wireframes - Concardis Service Connector

1.2 Version Information and Dependencies

This delivery and the accompanying documentation are valid for the following combinations of software versions:

* Please see PWA releases documentation for details.

The next table provides information about the cartridges included in the package. Not all of these cartridges are required.

Cartridge	Description	Required
ac_payment_concardis	Includes all base functionality and business logic which is used. Enables PayPal payment connector for the following application type: intershop.REST
as_responsive_concardis	Enables the Concardis payment connector for the following application types: intershop.B2CResponsive intershop.SMBResponsive The cartridge is optional, can be downloaded separately from Intershop Product Calendar and may be included if the project uses the responsive starter store. Unzip the file to your multi-project folder next to your responsive source files. This step can be skipped if the custom project does not support these application types or Concardis is not required in these application types.
app_sf_responsive_concardis	Includes some additional functionality which is relevant for the responsive storefront reference application only, e.g., the integration of the hosted payment pages of the credit card. The cartridge is optional, can be downloaded separately from Intershop Product Calendar and may be included in case the project is based on the responsive storefront reference application. Unzip the file to your multi-project folder next to your responsive source files. The referenced cartridge app_sf_responsive may be renamed in the project and has to be referenced in the build.gradle file with the customized naming again.

The Concardis Service Connector is based on the new Payment API introduced in IS 7.6.

The sources for as_responsive_concardis and app_sf_responsive_concardis can be downloaded here (use your repository login and password for authorization): https://repository.intershop.de//releases/com.intershop.public.source/s_payment_concardis/2.0.0/zips/s_payment_concardis-zip-src-2.0.0.zip

1.3 Supported Application Types

The Concardis Service Connector can be used for the following application types:

Documentation for Concardis error messages and possible sources of the errors is available here:

https://docs.payengine.de/buildyourown/restdoc/errors

Documentation for the REST API can be found here:

https://docs.payengine.de/buildyourown/restdoc/providercodes

3.1 Payment Methods

The Concardis Service Connector adds the following payment methods to your Intershop 7 system:

Payment Method Type	Payment Method	Auto Capture	Manual Capture*	Cancel*	Reduce*	Refund
Credit Card	Credit Card Payment supported by Concardis e.g.: Visa Mastercard American Express JCB Diners Club Includes 3DS 2.0 support.
Online Payment	Alipay
	Bancontact
	EPS
	Giropay
	iDEAL
	PayPal
	SEPA Direct Debit
	Sofort
	WeChat Pay

* only available if the corresponding payment method's Capture Mode is set to manual. Concardis reserves the authorized amount for a standard duration of 5 days. Afterwards a manual capture fails (error code 21).
The merchant can negotiate a different duration time with Concardis.

3.2 Payment Management Options

The following table lists all options that are available for payment transactions.

3.3 Synchronize Payment Transactions

The connector provides two options for manual synchronization of the payment states between Concardis and Intershop Commerce Management:

• A REST endpoint
• A Job (starting with version 1.1.4)

When a payment status was successfully synchronized with Concardis, the status is updated in ICM. Afterwards the order status is updated. In case the payment on Concardis side was successful, the order creation is continued at the point where it was broken. For failed payments the order is set to "PAYMENT_CANCELLED".

Orders which are pending on both sides (Concardis and ISH) cannot be fixed with that approach. In these cases there are abandoned baskets.

3.3.1 Job-Based Manual/Periodic Synchronization

To enable a periodic check if payments need to be synchronized, you have to configure a job in the SMC. Calling the startnode Start of pipeline SynchronizeConcardisPaymentsJob can be started manually or run regularly.

In the Attributes tab you can define after which time in the pending state (PendingSinceMins in minutes) a redirecting payment should be considered by the synchronization job and a status update from Concardis should be triggered.

The default value for the parameter PendingSinceMins is 30 minutes.

3.3.2 Manual Synchronization Using the REST Endpoint

For each order the administrator identified that it has an invalid state (payment status differs from Concardis), he has to copy the orderID from the Intershop Commerce Management URL (see screenshot below).

To trigger the synchronization call to Concardis, the administrator has to perform a REST request to the (temporary) API endpoint: /INTERSHOP/rest/WFS/inSPIRED-Site/inTRONICS/payment/concardis/synchronizations. The base URL is the same as in the ICM. In this example it is:  /INTERSHOP/rest/WFS/inSPIRED-Site/inTRONICS. Please use your own host and URL here.

Example call:

curl -X POST \
  http://<server>/<base-url>/payment/concardis/synchronizations \
  -u <order_manager>:<password> \
  -H 'Accept: text/plain' \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache' \
  -d '{"orderId" : "jfYKAB2_wIMAAAFuFd0.wqdp"}'

Alternatively, you can use the attached collection in the REST client Postman: Synchronize.postman_collection.json

All variables have to be replaced with data that is valid for your system. Instead of the user parameter an authorization header can be used for getting access to the endpoint. The administrator must have permissions to manage orders. This can be checked here:

5.1 Credit Card with Order Approval Service

Please be aware that Concardis Credit Card 3D Secure uses redirect after checkout. Intershop's current demo shop inSPIRED does not support a redirect after checkout if an order approval service in channel type intershop.SMBResponsive is enabled.

5.2 Partial Capture and Refund

Please be aware that partial capturing is only possible on Concardis side. Since the ICM only supports full capture in the commerce management, the refunds started from there cannot handle the fragmentation of the transactions. In case partial capturing via Concardis Merchant Interface is used, the refunding also has to be done there. The notifications will send updates to the ICM. If this is not considered and tried to refund an amount greater than the captured amount, the transaction will enter the final state "REFUND_FAILED".

5.3 Concardis Environments

It is important not to mix the types of the Concardis environment (Live/Sandbox). We recommend using the Sandbox environment in the testing system and the Live environment in the production system.

6 Noteworthy

• The Concardis Payengine declines requests with already used order IDs.
• Please note that hyphen signs in the order ID are not supported by some payment methods (e.g. Credit Card).
• When using the Cancel button in the Sandbox redirect page, the Payengine sends "Success" to the ICM and the order is completed successfully.
• Within the Concardis test environment, eps uses the giropay processing engine and therefore displays "giropay" instead of "eps" within the Concardis sandbox. This is a known issue by Concardis and acknowledged.
• When using the payment method PayPal in the Concardis sandbox, the failure button is missing in the simulated redirect. This is a known issue by Concardis and acknowledged.
• In contrast to Concardis documentation, initial order amounts of 1.11 or 111.11 will not trigger a negative response in the simulator. A charge-back on SEPA payments will be simulated.