Installing and configuring ArvatoEdit on GitHub
There is currently an issue when using giftcards with Arvato. Our team is developing a fix for it.
The purpose of developing the risk solution services is to provide a complete and comprehensive risk management for the eCommerce/mail-order industry, contributing to a high level of modularization and automation. Besides the use of pre-configured service modules for risk management, risk solution services comprise process support up to the outsourcing of the entire operative risk management. All risk management processes are supported by a business intelligence component.
For every service call of risk solution services an authorization is required. The authorization data is transferred in the SOAP header and shows the following structure.
In order to send requests, you are supposed to have the following credentials, provided by Arvato:
||Arvato RSS gateway.|
||Unique client number in the risk solution services. Will be communicated to the client before the integration|
||Password for the authorization at risk solution services|
||A map of payment names to ArvatoRss specific payment type codes.|
The following information (also present in
config.dist.php) should be specified in configuration:
ArvatoRssConstants::ARVATORSS_URL =& ''; ArvatoRssConstants::ARVATORSS_CLIENTID = ''; ArvatoRssConstants::ARVATORSS_AUTHORISATION =''; // Mapping of your payment methods to payment types, that are known by Arvato Rss. ArvatoRssConstants::ARVATORSS_PAYMENT_TYPE_MAPPING => [ 'invoice' => ArvatoRssPaymentTypeConstants::INVOICE ];
To implement Arvato RSS you should be familiar with concept of extending the Spryker Commerce OS. See Extending Spryker for more details.
To install Arvato RSS module, use Composer:
composer require spryker-eco/arvato-rss
For submitting the form