After
installing the plugin, a new menu item CRIF appears in the admin area under
Settings / Extensions.
• the access data are entered here in
the first step
• then click on the Button
"query API" button
• the access data will now be
validated (test for plausibility of entered values)
After
success, depending on the activated access, the possible configuration settings
and control parameters for product family b.ONE or OrderCheck appear.
When you
switch the module live for the first time or change the interface, be sure to
check the correct functionality using live or test data.
Configuration
settings for b.one
Credit
check in the checkout
Checking
the selected payment method
The
selected payment method check checks whether the payment method is available
for the customer only after the order has been submitted. If the payment method
is excluded for him, he will be redirected back to the payment method
selection. Please note the special
features of the rule structure.
Germany
timeout in seconds / International timeout in seconds
Define a
timeout for the request to the CRIF API
Re-verification
of existing customers after [days
The number
of days after which the risk assessment of an existing customer will be
performed again. This is how long the previously determined result is used for
decisions.
Caching
within the session
If caching
is set to Yes, a request once made is remembered within a frontend session.
Product
Select
whether underwriting should be performed for consumers and companies.
ConCheck
Product
Select the
appropriate ConCheck product for underwriting.
RickCheck
Product
Select the
appropriate RiskCheck product for underwriting.
Shopping
cart value difference [%]
If there is
a difference in the shopping cart value beyond this percentage, a new inquiry
will be made.
Check
Germany
Activate/deactivate
here the check for Germany
Check
Switzerland
Activate/deactivate
here the check for Switzerland
Check
Austria
Activate/deactivate
the check for Austria here
Log
personal data?
Personal
data should only be logged for debugging purposes.
Exclude
customer group from check
Select the
customer groups to be excluded from the check.
Configuration
settings for OrderCheck
Risk
assessment in the checkout
Checking
the selected payment method
The
selected payment method check checks whether the payment method is available
for the customer only after the order has been submitted. If the payment method
is excluded for him, he will be redirected back to the payment method
selection. Please note the special
features of the rule structure.
Germany
timeout in seconds / International timeout in seconds
Define a
timeout for the request to the CRIF API
Re-verification
of existing customers after [days]
The number
of days after which the risk assessment of an existing customer will be
performed again. This is how long the previously determined result will be used
for decisions.
Caching
within the session
If caching
is set to Yes, a request once made is remembered within a frontend session.
Product
Select the
appropriate product(s) for underwriting.
Shopping
cart value difference [%]
If there is
a difference in the shopping cart value beyond this percentage, a new inquiry
will be made.
Check
Germany
Activate/deactivate
the check for Germany here.
Check
Switzerland
Activate/deactivate
the check for Switzerland here and enter the corresponding login data
Check
Austria
Activate/deactivate
the check for Austria here and enter the corresponding login data
Check
Belgium
Activate/deactivate
the check for Belgium here and enter the corresponding login data
Check
Sweden
Activate/deactivate
the check for Sweden here and enter the corresponding login data
Check
Finland
Activate/deactivate
the check for Finland here and enter the corresponding login data.
Check
Norway
Activate/deactivate
the check for Norway here and enter the corresponding login data.
Check
Netherlands
Activate/deactivate
the check for the Netherlands and enter the corresponding login data.
Check
Denmark
Activate/deactivate
the check for Denmark here and enter the corresponding login data.
Request
personal number
For Sweden,
Finland and Norway it is necessary to enter a personal number. If you activate
this, the frontend view will be extended.
Log
personal data?
Personal
data should only be logged for debugging purposes.
Exclude
customer group from check
Select the
customer groups that should be excluded from the check.
Rule
setting in the Rule Builder
After
installation, new rule parameters are in the RuleBuilder of Shopware.
rule
settings for b.ONE
Score
The CRIF
Score from a RiskCheck/CreditCheck: The score is displayed in the module with a
value between -1 and 60. The score = -1, is considered as an error case. A
score = 0 indicates that no data is available for the requested data set. The
score can be defined as equal to greater than, greater than/equal to, less
than, less than/equal to, and not equal to, etc. as a rule.
b.ONE
identification
The b.One
identification can be defined as one or more separated values (comma
separated). The codes of the b.ONE identification have the following meaning:
ConCheck
N0
person
unknown
NW
person
unknown/adress bekannt
N1
person/adress
known
N2
person/adress
different
To define a
rule that should apply only when a person is identified, we recommend using the
codes N1, N2: the person was identified uniquely or with a different address.
If a rule
is to apply when a person has not been identified, then the codes NW, N0 should
be used.
RiskCheck
A0
company/person
unknown
A1
company/adress
known
A2
company/adress
different
A3
person/adress
known
A4
person/adress
different
A5
person
unknown/adress known
A6
serveral
companies known
To define a
rule that should apply only if a company/person is identified, we recommend
using codes A1, A2, A3 and A4: the company/person has been identified uniquely
or with a different address.
If a rule
is to apply when a company/person has not been identified, then codes A0, A5
and A6 should be used.
Note: If
both products (ConCheck and RiskCheck) are used, then the codes of both
products must be used.
Product
group
The product
group is selected by a number. 1 stands for ConCheck, 2 for RiskCheck or 1,2
for both.
The product
group must be selected if certain rules should only apply to one product group.
Eror case
In case of
error or communication problems with CRIFs, the module sets the
ConCheck/RiskCheck score to -1. If all payment types should be displayed in
case of error, a rule "Score=-1" can be defined. Otherwise, the
corresponding payment type will not be displayed in the event of an error.
Note: If
valid decision values (i.e. the age of the last successful check is less than
the set days until a new check of existing customers) already exist for a
customer in the store, these existing results are used for a payment type
control. In this case, the customer only receives the payment types for
selection that would also be available without errors.
rule
settings for OrderCheck
traffic
light decision
The traffic
light decision from the OrderCheck request, this is either RED, YELLOW or
GREEN. The traffic light decision can be
defined with equal, greater/equal, smaller, smaller/equal, unequal etc. in the
rule. Where here GREEN is greater than YELLOW is greater than RED.
Example: a
rule to show a payment type for YELLOW and GREEN would then be: "traffic
light decision greater/equal YELLOW".
Rating
Available only for CreditCheckONE product or after agreement with CRIF.
The rating
is a decision returned by OrderCheck from best rating AAA to worst rating CCC.
The exact order of the rating is as follows: AAA, AA, A, B, BB, BBB, C, CC,
CCC, where AAA is the highest rating and CCC is the lowest rating. The rating
can be defined as equal, greater than/equal to, less than/equal to, unequal to,
etc. in the rule.
Example: a
rule to indicate a number type at AAA, AA, A would then read:
"Rating greater than/equal to A".
Limit is
only available in consultation with CRIF.
Defines a
customer-specific limit determined, which can be included in the decision of
the granted payment types.
Actual
payment type Is only available in consultation with CRIF.
Defines a
list (comma separated) of payment types that must be included in the OrderCheck
response for this query.
Actual
product group
The product
group is selected by a number. 1 represents CreditCheckConsumer, 2 represents
CreditCheckBusiness, or 1,2 represents both. The product group must be selected
if certain rules should only apply to one product group.
Error case
In case of
error or communication problems with CRIF, the module sets the OrderCheck
rating to -1 and the traffic light decision to NONE. If all payment types
should be displayed in case of error, a rule "Traffic light
decision=NONE" or "Rating =-1" can be defined. Otherwise, in
case of an error, the corresponding payment type will not be displayed. Please
only set a rule on the rating if you have also agreed on a rating as a return
with Crif.
Note: If
valid decision values (i.e. the age of the last successful check is less than
the set days until a new check of existing customers) already exist for a
customer in the store, these existing results are used for a payment type
control. In this case, the customer only receives the payment types for
selection that would also be available without errors.
Rule
setting for the setup of the "Active control of the payment type".
https://docs.shopware.com/de/shopware-6-de/einstellungen/regeln
For the active
control of the payment type, the standard function in Shopware 6 can be used
for the rule setting. Accordingly, enter as type: payment type. For the
associated payment type in the availability rule enter the defined rule.
Rule
setting for the setup of the "Check the selected payment method"
The check
of the selected payment method only takes effect after order completion and can
therefore not be handled according to the Shopware standard rule system for
payment methods.
In order to
be able to perform a CRIF risk check after selecting the payment method, the
rules in the Rule Builder must meet the following requirements:
1. the name of the rule must start with
"CRIF-RULE"
2. the description of the rule must
contain the name of the payment type to which the rule is to be applied. One
payment type per line. In case of a multilingual store, each language must be
entered for which the rule is to apply.
3. the condition on which parameters the
decision should be based is selected as known
Example for
OrderCheck: Create rule, e.g. allow purchase on account with traffic light =
GREEN
IMPORTANT:
Normally
Shopware's own rules, which should result in certain payment types not being
available for selection in the first place, are assigned to the payment types
directly under Shop-> Payment types -> Availability rule.
This
assignment must NOT be done for the "CRIF-RULE" rules, which are
based on the CRIF check and should apply to the passive payment type control!
Rules that
contain Shopware's own parameters can be further set here. This would then
result in these payment types not being selectable in the first place.
Example:
Payment
type Invoice has an availability rule "Shopping cart < 1000", then
the payment type Invoice would only be displayed if the shopping cart value is
less than 1,000, completely independent of the CRIF check.
If the
above-mentioned CRIF-RULE for Invoice were then also set, the payment type
"Invoice" would be displayed for shopping carts < 1,000 and lead
to a check when selected by the customer.
For
shopping carts >= 1,000, the customer could not select the invoice payment
method at all and thus no check could be made.
View
decision values for customers
To view the
result of the risk assessment, such as score/rating/ramp decision for a customer,
click on "Customers" > "Customers" in the Shopware
backend and then select the desired customer by clicking on the pencil.
CRIF
exclusion:
If active,
no underwriting will be performed for this customer.
Query Time:
UTC time of
query.
CRIF-Score:
The result
of the last CRIF risk check.
CRIF-Text:
The
response text of the last query.
Person Number:
The person
number for the check in Scandinavian countries.