Installing and configuring Arvato
Edit on GitHub
You are browsing a previous version of the document. The latest version is 202212.0.
There is currently an issue when using giftcards with Arvato. Our team is developing a fix for it.
Prerequisites
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:
Parameter Name | Description |
---|---|
ARVATORSS_URL |
Arvato RSS gateway. |
ClientID |
Unique client number in the risk solution services. Will be communicated to the client before the integration |
Authorization |
Password for the authorization at risk solution services |
ARVATORSS_PAYMENT_TYPE_MAPPING |
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
];
API URLs:
Name | URL |
---|---|
Production URL | https://customer.risk-solution-services.de/rss-services/risk-solution-services.v2.1 |
Sandbox URL | https://integration.risk-solution-services.de/rss-services/risk-solution-services.v2.1 |
Services:
To implement Arvato RSS you should be familiar with concept of extending the
Installation
Composer Dependency
To install Arvato RSS module, use Composer:
composer require spryker-eco/arvato-rss
Thank you!
For submitting the form