Boniversum

Logo

Info

Boniversum supports merchants with credit ratings for consumers. The data from the credit agency help to evaluate non-payment risks and to adapt the methods of payment according to the credit prognosis.

Type

Risk Management

Format

Description

a

alphabetical

as

alphabetical with special characters

n

numeric

an

alphanumeric

ans

alphanumeric with special characters

ns

numeric with special characters

bool

boolean expression (true or false)

3

fixed length with 3 digits/characters

..3

variable length with maximum 3 digits/characters

enum

enumeration of allowed values

dttm

ISODateTime (YYYY-MM-DDThh:mm:ss)

Abbreviation

Description

Comment

CND

condition

M

mandatory

If a parameter is mandatory, then it must be present

O

optional

If a parameter is optional, then it can be present, but it is not required

C

conditional

If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

ans..30

O

Unique reference number

OrderDesc

ans..768

M

Description of purchased goods, unit prices etc. Reference for customer and merchant.

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

• HMAC Authentication (Request)

• HMAC Authentication (Notify)

ProductNr

n..4

M

Product ID (communicated by Boniversum in advance)

RequestReason

n2

O

Justified interest

In order to be allowed to make requests in accordance with the Federal Data Protection Act (BDSG), you must have a so-called ‘justified interest’ (BDSG Article 29 Section 2) in order to be able to retrieve a person’s stored data.

01: Credit decision

03: Initiation of business

04: Receivable

05: Insurance contract

06: Ownership structure

07: Overdue receivables

08: Information about execution

09: Terms request (BDSG, Article 28a Section 2 Sentence 4) (financial services sector only)

Consent

n1

M

Consent clause

According to the regulations of the Federal Data Protection Act, Boniversum is obligated (BDSG Article 4a) to check that the person who is the subject of the enquiry has consented to the storage of the data which is the subject of this enquiry. To this end it is necessary to select ‘Consent given’ in the box for the enquiry. If a Boniversum consent clause signed by the consumer exists, the fact of the enquiry as a so-called ‘Enquiry data record’ is also stored in the Boniversum system (whereas this is not possible in the case of selecting “Consent not given”.

In the case of selecting “Consent not given”, a check will also be made to establish whether Boniversum is already is possession of an earlier consent given by the consumer. If data are transmitted for the first time from Boniversum to third parties without the consumer having previously learned of the storage of his/her data at Boniversum by means of a signed consent clause or in some other way, the consumer will be informed by standard letter of the first transmittal of his/her data by Boniversum following the issuing of the information.

0: Consent not given

1: Consent given

Gender

a1

M

Gender: <m> male, <f> female

FirstName

ans..50

M

First name

LastName

ans..50

M

Last name

MiddleName

ans..50

O

Middle name

DateOfBirth

n8

O

Date of birth in the format YYYYMMDD

MaidenName

ans..50

O

Maiden name

AddrStreet

ans..50

M

Street name

AddrStreetNr

ans..15

M

Street number

AddrZip

n..10

M

Postcode

AddrCity

ans..50

M

City

AddrStreet2

ans..50

O

further street name

AddrStreetNr2

ans..15

O

further street number

AddrZip2

n..10

O

further postcode

AddrCity2

ans..50

O

further town/city

mid

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

OrderDesc

ans..768

M

Description of purchased goods, unit prices etc. Reference for customer and merchant.

Status

a..50

M

OK or FAILED

The merchant needs to take his own decision based on ScoreWert and Result, because Status=OK means only that the request was successful.

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

an8

M

Error code according to Paygate Response Codes (A4 Error codes)

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

CodeExt

ans..40

O

Error code from Boniversum, if agreed with Computop Helpdesk

ErrorText

ans..256

O

Error text from Boniversum, if agreed with Computop Helpdesk

Reference

ans..18

O

Reference number from Boniversum (order number)

ScoreWert

n..5

O

Score value

Result

a..16

O

Result as traffic light value

green = accept. There are no personally related negative attributes

yellow = caution!

red = there are negative data for this person

If the value is not displayed, this means that there is insufficient data for a calculation.

AddrStreet

ans..50

O

Street name

AddrStreetNr

ans..15

O

Street number

AddrZip

n..5

O

Postcode

AddrCity

ans..40

O

City

Match

n..2

O

The check is done according to postal correctness of submitted address (postcode, city, street) and is independent of individuals.

01 = The submitted address was postally validated.

02 = The submitted address was postally corrected and validated.

03 = The submitted address could not be validated postally.

CountryCode

ans..2

O

Country code