Public Release Note - Concardis Service Connector 1

1 Introduction

Welcome to the Intershop Concardis Service Connector. The service connector adds Concardis payment methods to your Intershop installation.

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

1.1 References

1.2 Version Information and Dependencies

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

Intershopsupported Application TypesPWA*Concardis Service Connector
7.10.15.3intershop.SMB, intershop.B2C0.17.0+

1.1.5

7.10.16.6intershop.SMB, intershop.B2C0.17.0+1.3.0+
7.10.16.6+intershop.SMB, intershop.B2C0.20.0+1.7.0+
7.10.16.6+intershop.SMB, intershop.B2C0.20.0+1.9.0+
7.10.17.0+intershop.SMB, intershop.B2C, intershop.REST**0.20.0 - 0.23.01.10.8+
7.10.26.2-LTS+intershop.SMB, intershop.B2C, intershop.REST0.26.0+1.11.7+ (planned version)

* Please see PWA releases documentation for details.

** Feature of ICM 7.10.21.0

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

CartridgeDescriptionRequired
ac_payment_concardisIncludes all base functionality and business logic which is used.(tick)
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.

(error)
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.

(error)

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/1.10.8/zips/s_payment_concardis-zip-src-1.10.8.zip

1.3 Supported Application Types

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

Application TypeApplication Type IDDescription
B2C WebShopintershop.B2CResponsiveBusiness to Consumer Channel
SMB WebShopintershop.SMBResponsiveBusiness to Business Channel
Progressive Web Appintershop.RESTBusiness to Customer and Business Channel via REST API
(only available with ICM 7.10.21 and later)

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

2 Setup

This section outlines the basic setup and configuration steps, including

Note

Managing and deploying the Concardis Service Connector requires a continuous integration environment set up and configured as described in Cookbook - Setup CI Infrastructure.

2.1 Preconditions

The package is available via Intershop's Public Repository (Artifactory). Furthermore, the following preconditions are required:

  • A set up and configured CI environment
    See Cookbook - Setup CI Infrastructure for details.
    See Concept - Continuous Delivery Tools for basic information about continuous integration.
  • A running Intershop Commerce Management 7.10 installation that matches the system requirements
  • Knowledge of how to add the delivered artifacts to the continuous integration environment
  • Knowledge of how to deploy to a test or production environment

2.2 Setting Up the Assembly

To add the Concardis Service Connector into your Intershop 7 system, you can either incorporate the cartridge into an already existing assembly or create a new assembly inheriting from an Intershop-7-based assembly. For details about creating a new assembly, see Recipe: Create a New Assembly Inheriting From an Existing Assembly. If you want to incorporate the cartridge into an already existing assembly, perfom the following steps:

  1. Add the following to the build.gradle file of the assembly:

    ...
     
    cartridges {
            def storefrontCartridges = [
                'app_sf_responsive',
                'app_sf_responsive_cm',
                'app_sf_responsive_b2c',
                'app_sf_responsive_smb',
                'as_responsive',
                'app_sf_responsive_b2b',
                'app_sf_responsive_costcenter',
                'as_responsive_b2b',
    // this are the two cartridges, which we delivered in source code and you have to add these files to your responsive source project
                'as_responsive_concardis',
                'app_sf_responsive_concardis'
               ]
            include(*(storefrontCartridges.collect { project(":$it") }), in:[development, test, production])
      
    ...
     
            def concardisPaymentProvider = [
                'ac_payment_concardis', 
            ]
            include (*(concardisPaymentProvider.collect {"com.intershop.services.payment_concardis:$it"}), in: [development, test, production])    
      
            order = listFromAssembly(baseAssembly) + concardisPaymentProvider 
        }
    ...
    assemblyBuild {
        database {
            inherit(<yourAssembly>)
            initCartridges = []
        }
    }
    ...
    
  2. Adapt the app_sf_responsive_concardis/build.gradle file in the following way:

    apply plugin: 'static-cartridge'
     
    intershop
    {
           displayName = 'Adapter - Payment Concardis - Business Extensions'
    }
     
    dependencies
    {
    //   compile project(':ac_payment_concardis') --> will be replaced by
         compile group: 'com.intershop.services.payment_concardis', name: 'ac_payment_concardis'
    
       compile group: 'com.intershop', name: 'api_service'
    ...
    }
    
    
  3. Adjust the file as_responsive_concardis/build.gradle in a similar way:

    ...
    dependencies {
    //  compile project(':ac_payment_concardis') --> will be replaced by 
        compile group: 'com.intershop.services.payment_concardis', name: 'ac_payment_concardis'
        compile project(':app_sf_responsive_concardis')
    }
    ...
  4. Insert the following lines into the file: intershopBuild.version

    com.intershop.services.payment_concardis:ac_payment_concardis = 1.10.8

    For details about adding components to an assembly, see Recipe: Add Cartridges to an Assembly.

For details about managing assembly artifacts see:

2.3 Defining File-Based Configuration

Before deploying the new assembly to a test or production environment, you may have to adjust some file-based configurations required by the Concardis Service Connector.

The Concardis Service Connector requires the following settings:

PropertyDescriptionValue
intershop.payment.Concardis.apiBaseUrl.sandbox

Defines the base URL used for requests to the Concardis sandbox. Default: https://apitest.payengine.de/v1

Leave at default value unless URL of API endpoint on Concardis changes.

URL to the sandbox (provided by Concardis)
intershop.payment.Concardis.apiBaseUrl.live

Defines the base URL used for requests to the Concardis live environment. Default: https://api.payengine.de/v1

Leave at default value unless URL of API endpoint on Concardis changes.

URL to the live system (provided by Concardis)
intershop.payment.Concardis_CreditCard.currenciesDefines which currencies are configurable for Concardis Credit Card. Default: * (all currencies)comma-separated list, e.g., EUR, USD

intershop.payment.Concardis_CreditCard.cvcmaxage

( only in Concardis 1.11.x and newer )

Defines the maximum time for which CVC remains valid in minutes. The value must be smaller or equal to the valid time on Concardis side (30 minutes). Default: 25 (minutes)Integer, e.g. 25
intershop.payment.Concardis_EPS.currenciesDefines which currencies are configurable for Concardis EPS. Default: EURcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_Giropay.currenciesDefines which currencies are configurable for Concardis Giropay. Default: EURcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_iDEAL.currenciesDefines which currencies are configurable for Concardis iDEAL. Default: EURcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_PayPal.currenciesDefines which currencies are configurable for Concardis PayPal. Default: * (all currencies)comma-separated list, e.g., EUR, USD

intershop.payment.Concardis.DirectDebit.countries

Defines which currencies are configurable for Concardis SEPA Direct Debit. Default: EURcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_Sofort.currenciesDefines which currencies are configurable for Concardis Sofort. Default: EUR, CHFcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_Alipay.currenciesDefines which currencies are configurable for Concardis Alipay. Default: AUD,CAD,EUR,GBP,HKD,SGD,USD,NZDcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_WeChatpay.currenciesDefines which currencies are configurable for Concardis WeChat Pay. Default: EUR, USD, GBPcomma-separated list, e.g., EUR, USD
intershop.payment.Concardis_Bancontact.currenciesDefines which currencies are configurable for Concardis Bancontact. Default: EURcomma-separated list, e.g., EUR, USD


According to Recipe: Change Deployed File Content With Filters this setting has to be overridden within <IS_SHARE>/system/config/cartridges/ac_payment_concardis.properties.

For details about adding new configuration files, see Recipe: Deploy Custom Files.


Additionally, the countries where a payment method is available can be defined in <IS_SHARE>/system/cartridges/ac_payment_concardis/release/config/countriesConfigurations.properties. The values can be defined as whitelist or blacklist.

PropertyDescriptionValue
intershop.payment.Concardis.CreditCard.countriesDefines for which country of the invoice address the payment method Credit Card is available. Default: * (all countries)comma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.EPS.countries

Defines for which country of the invoice address the payment method EPS is available. Default: AT

comma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.Giropay.countriesDefines for which country of the invoice address the payment method Giropay is available. Default: DEcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.IDeal.countriesDefines for which country of the invoice address the payment method iDEAL is available. Default: NLcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.PayPal.countriesDefines for which country of the invoice address the payment method PayPal is available. Default: * (all countries)comma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.DirectDebit.countriesDefines for which country of the invoice address the payment method SEPA Direct Debit is available. Default: DE, CH, ATcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.Sofort.countriesDefines for which country of the invoice address the payment method Sofort is available. Default: DE, AT, CH, NL, BE, ES, ITcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.Alipay.countries.excludeDefines for which country of the invoice address the payment method Alipay is not available. Default: CNcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.WeChatpay.countries.excludeDefines for which country of the invoice address the payment method WeChat Pay is not available. Default: CNcomma-separated list of 2-digit country codes (ISO 3166-1)
intershop.payment.Concardis.Bancontact.countriesDefines for which country of the invoice address the payment method Bancontact is available. Default: BEcomma-separated list of 2-digit country codes (ISO 3166-1)

The values are dependent on the supported countries for these payment methods by Concardis.

2.4 Deploying the Assembly

After creating and appropriately configuring the assembly, you must deploy it to the intended target environment.

For details about deploying an assembly, see Recipe: Run the Deployment (Initial Installation / Upgrade / Downgrade).

Note

The Concardis Service Connector requires additional post-deployment configuration steps. For details, refer to Configuration .

3 Customization

3.1 Adding a Custom Applicability Check

It is possible to add a custom applicability check in order to display the payment method only if additional conditions are met.

To provide a custom check in one of the payment methods (e.g., CreditCard), you need to create a new class:

CustomCreditCardApplicabilityCheckImpl
public class CustomCreditCardApplicabilityCheckImpl implements ApplicabilityCheck
{
    @Override
    Result<ApplicabilityResult> getApplicability(Payable payable, String serviceName, BaseConfiguration baseConfiguration);
    {
		Result<ApplicabilityResult> result = new Result<>(new ApplicabilityResult());
        result.setState(ApplicabilityResult.APPLICABLE);

		boolean customConditionMet = true; // do your additional checks, e.g. based on data in `Payable`
		if (! customConditionMet )
		{
			result.setState(ApplicabilityResult.NOT_APPLICABLE);
		}
		return result;
    }
}

The current Payable is handed in, so you can compute the applicability of the payment method based on the data.

Then you need to bind your class in a custom Guice Module. In this case it has to be something like this:

Multibinder<ApplicabilityCheck> applicabilityBinder = Multibinder.newSetBinder(binder(), 
                        ApplicabilityCheck.class, named("Concardis_CreditCard_ApplicabilityChecks"));
applicabilityBinder.addBinding().to(CustomCreditCardApplicabilityCheckImpl.class).in(Singleton.class);

4 Configuration

This section outlines the required post-deployment configuration steps, including

4.1 Applying UI-Based Configuration

The Concardis Service Connector requires some post-deployment configurations in the Organization Management application and in the Commerce Management application.

For details about enabling a payment service see Cookbook - Payment | Recipe: Enable a Payment Service.

4.1.1 Assign Payment Services to a Sales Organization

ExplanationImage

Log in to Organization Management.

1. Navigate to Sales Organizations.

2. Select the name of the organization.


3. Go to Services.

4. Click Payment Services.



5. Select the checkboxes of the new payment methods
you intend to enable for the current sales organization.

6. Click Enable.

4.1.2 Create a Managed Payment Service

ExplanationImage

Log in to Commerce Management.

1. Select the Organization/Channel.

2. Go to Services.

3. Click New.


4. Select the new payment service.

5. Click Next.


6. Enter a Payment Service Name.

7. Enter "Service ID".

8. Select the checkbox Active.

9. Select the checkbox Available.

10. Click Next.


Precondition for step 11 is access to the Payengine Merchant Center.
The CSS file has to be customized to style the Credit Card and CVC input field,
which will be displayed to the customer in the checkout payment step.



11. Enter all Concardis general settings.

Card Number Style ID and CVC Style ID are mandatory when using the PWA (Progressive Web App Storefront).

12. Enter all logging settings.

13. Enter all monitoring settings.

14. Click Next.

15. Select the Sharing Rule.

(When setting up in the organization area, the service
must necessarily be shared to the channel.)

16. Click Finish.


The table below lists Concardis-specific settings for configuring the payment service.

NamePayment MethodsDescription
Merchant IDAllThe merchant account's merchant ID as provided by Concardis
API KeyAllThe merchant account's API Key as provided by Concardis
System health status expiration time

All

Insert the time interval in seconds which checks if the Payengine service is available. If the service is offline, the payment methods are hidden at the payment page in the checkout.
Card Number Style IDCredit CardIn the Concardis Merchant Center the Credit Card input field can be styled with CSS class. Enter the Style ID which was generated in the Merchant Center here.
CVC Style IDCredit CardIn the Concardis Merchant Center the CVC input field can be styled with CSS class. Enter the Style ID which was generated in the Merchant Center here.
CaptureAllCapture "Auto" will automatically do authorization and capture in one step. Capture "Manual" separates authorization from capture process, so capture has to be done manually at the order when the items are shipped.
EnvironmentAllDefines whether "Sandbox" for test and development is used or "Live" for production.
Submit Order DetailsAllThis enables or disables the ability to send all product line items information to Concardis.
Submit Address DetailsAll

This enables or disables the transfer of the address to Concardis. Enable for transmitting the address data to Concardis. If enabled, the custom field mapping below has to be provided. 

Please leave this setting disabled in case the address is stored as single attribute on ICM side.

Street MappingAllOnly required if the option "Submit Address Details" was enabled. Maps an address line to the field "street" on Concardis side. 
House Number MappingAllOnly required if the option "Submit Address Details"  was enabled. Maps an address line to the field "house number" on Concardis side. 


4.1.3 Configure the Payment Methods

Note

Configuring payment methods in a sales channel requires the access privilege Payment Manager for this channel.

Explanation

To enable the payment method for the channel,
log into Commerce Management and perform the following steps:

1. Select the context selection box.

2. Select the sales channel.

3. Click Orders.

4. Click Payment Methods.

5. Click New.

6. Enter Payment Method ID.

7. Select the Configuration Type.
The type was created in the section Create a Managed Payment Service.

8. Click Apply.

9. Click Applications.

10. Select the checkboxes of all applications
for which the payment method should be enabled.

11. Click Enable.

12. Click Payment Costs.

13. Define taxation class, currency, minimum order value, amount
and/or threshold for the payment method if desired and click Add.

14. Click Apply.

15. Click Customer Segments.

16. Enable the target customer segments.

17. Click Apply.

18. Click Preferences.

19. Select the currency-dependent availability and the payment currency.

20. Click Apply.

4.2 Localization

The Concardis Service Connector provides English, French and German localization files for payment-specific input field labels. 

You can find the existing localization files here: <IS.INSTANCE.SHARE>/system/cartridges/ac_payment_concardis/release/localizations.

For details about localization see Concept - Localization.

4.3 Adjusting Firewall Settings

Adjust your firewall settings to allow bidirectional HTTPS traffic between Intershop 7 and Concardis. Make sure that the <host>:<port>/INTERSHOP/rest/WFS/inSPIRED-inTRONICS-Site/-/concardis/notifications/*  is accessible from the Concardis IP addresses only. Please contact your Concardis account manager to ask for more details about the valid IP addresses.


5 Feature Overview

5.1 Payment Methods

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


Payment Method TypePayment MethodAuto CaptureManual 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.

(tick)(tick)(tick)(error)(tick)
Online PaymentAlipay(tick)(error)(error)(error)(tick)

Bancontact(tick)(error)(error)(error)(tick)

EPS(tick)(error)(error)(error)(error)

Giropay(tick)(error)(error)(error)(error)

iDEAL(tick)(error)(error)(error)(tick)

PayPal(tick)(tick)(tick)(tick)(tick)

SEPA Direct Debit(tick)(tick)(tick)(tick)(error)

Sofort(tick)(error)(error)(error)(error)

WeChat Pay(tick)(error)(error)(error)(tick)

* 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.

5.2 Payment Management Options

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

OperationDescription
CaptureRequest for settling the payment. This action is only available if the corresponding payment method's Capture Mode is set to manual.
CancelRequest for abandoning a payment settlement. This action is only available if the corresponding payment method's Capture Mode is set to manual.
RefundOption to return (parts of) the captured amount. This action is only available if the corresponding payment transaction was captured before.
ReduceRequest for reducing the authorized payment amount partially. This action is only available if the corresponding payment method's Capture Mode is set to manual.

5.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.

5.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.

5.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:

6 Limitations

6.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.

6.2 REST API Support

REST support for redirect after checkout is available starting with ICM 7.10.13.4 release.

6.3 New Headless Application Type

There was a new application type "Progressive Web App" introduced with ICM 7.10.21 and made default for usage within PWA 0.23.0. The new application type is not supported yet by the connector 1.10.x. Usage may lead to faulty handling in the PWA when using Credit Card or Direct Debit. To restore the old handling the previous used application type has to be enabled again. To achieve this , the PWA 0.23.0 entry 

icmApplication: 'rest'

in the PWA file environment.ts has to  be set back to

icmApplication: '-'

The new headless application type will be supported out of the box with Concardis version 1.11 and higher in combination with PWA 0.25.0++.

PWA 0.24.0 and concardis 1.10 are not compatible at all due to different feature set development states.

6.4 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 goes into the final state "REFUND_FAILED".

6.5 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.

7 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 Concardis test environment, eps is using 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.

8 Changelog

8.1 Version CONCARDIS/1.11.7 (planned version)

  • Added support for saving credit cards and SEPA direct debit accounts for later reuse

8.2 Version CONCARDIS/1.10.8

  • Fix CONCARDIS-384: Concardis payment is shown on zero money payment

8.3 Version CONCARDIS/1.10.7

  • Fix CONCARDIS-379: Header Accept Type incompatible with Concardis notifications

8.4 Version CONCARDIS/1.10.6

  • New payment method: Bancontact

8.5 Version CONCARDIS/1.9.8

8.6 Version CONCARDIS/1.9.7

  • New payment method: Alipay
  • New payment method: WeChat Pay
  • Improvement of address transmission with mapping of address fields

8.7 Version CONCARDIS/1.7.6

  • Fix CONCARDIS-298: Notification URLs are invalid when no ServerGroup is provided
  • Fix CONCARDIS-308: DirectDebit not usable without CreditCard

8.8 Version CONCARDIS/1.7.2

  • Support ICM 7.10.17.x
  • Provide access to prepared SEPA mandate text via REST

8.9 Version CONCARDIS/1.7.0

  • New payment method: SEPA Direct Debit
  • New payment method: Sofort
  • New feature: transmission of line items to Concardis
  • New feature: transmission of addresses to Concardis

8.10 Version CONCARDIS/1.3.2

  • Release including PayPal payment method
  • Support of 3DS 2.0 for credit card payments
  • New feature: support for Concardis Notifications API 2.0

8.11 Version CONCARDIS/1.1.5

  • Fix CONCARDIS-214: Specific REST request causes the ICM Storefront REST API to crash

8.12 Version CONCARDIS/1.1.4

  • New Feature: possibility to sync payment transactions with Concardis using a job.

8.13 Version CONCARDIS/1.1.3

  • New Feature: possibility to sync payment transactions with Concardis which is needed for some transactions until notification handling is available and integrated. See usage description in the Feature Overview.

8.14 Version CONCARDIS/1.1.2

  • Release including EPS, iDEAL and GiroPay payment methods

8.15 Version CONCARDIS/1.0.0

  • First Release including Credit Card payment method

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources
Tickets