• DeutschEnglish

Credorax

Logo

Info

Credorax

Type

Payments by Credit Card

Introduction

For more information about acquirers and connection, integration with Computop Paygate and Implementation of 3-D Secure (2.x), see chapter Card processing - common introduction.

Specific parameters for Credorax

Besides the general parameters described above for the credit card connection, Credorax requires the following additional parameters. An authorisation with 3-D Secure is possible.

Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :

Key

Format

CND

Description

TransID

ans..40

M

TransactionID which should be unique for each payment

RefNr

ns..30

M

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

OrderDesc

ans..64

M

Description of purchased goods, unit prices etc.

UserData

ans..1024

O

If specified upon call, Paygate forwards the parameter with the payment result to the shop

CHDesc

ans..34

O

Text printed on the customer’s credit card bill.

This function must be enabled by Credorax and have the following structure.

  1. merchant DBA name (up to 20 characters)2) asterisk3) additional text (up to 13 characters).

e.g. Computop*Test

This value can be alternatively permanently defined by Computop Helpdesk

AccVerify

a3

O

If AccVerify=Yes the card will be checked at the acquirer according to the acquirer’s interface description. The merchant has to submit only this parameter, the parameter "Amount" is optional. If  "Amount" is used we replace the amount according to acquirer’s interface description. At payment always Amount=0 is stored.

Allowed value: yes

RTF

a1

O

for repeat payments (subscriptions): I = Initial payment of a new subscriptionR = Routine payment (Recurring)

InvoiceNr

an..15

C

Invoice number. Mandatory for initial payment of a new subscription (RTF=I) or for generating a PCN

TokenExt

an..32

OC

In connection with RTF=R the Token must be transmitted for referencing the credit card data.

Contact data/Address verification (AVS)

CreditCardHolder

a..50

O

Name of the card holder

AddrStreet

ans..50

O

Street name (for AVS)

AddrStreetNr

n..16

O

Street number (for AVS)

AddrZip

ans..9

C

Postcode. Mandatory for initial payment of a new subscription (RTF=I) or for generating a PCN/TokenExt.

AddrCity

ans..30

O

Town

AddrState

a2

O

Federal State, two-digit code according to ISO 3166

AddrCountryCode

a2/a3

C

Country code according to ISO-3166-1, alphanumeric 2 or 3 chars.

Mandatory for initial payment of a new subscription (RTF=I) or for generating a PCN/TokenExt.

Phone

ns..32

O

Telephone number

Email

ans..64

C

E-mail address. Mandatory for initial payment of a new subscription (RTF=I) or for generating a PCN/TokenExt and if CFT (Credit Funds Transfer) is used.

UK 6012 Merchant Mandatory for UK merchants with MCC 6012

DateOfBirth

n8

M

Date of birth of the customer in format YYYYMMDD

AccNr

n..10

M

Masked PAN, account number or customer number

AddrZip

ans..6

M

Postcode of the customer

LastName

ans..6

M

The first six characters of the last name of the customer

Additional parameters for credit card payments

The following table describes the result parameters with which the Computop Paygate responds to your system.

these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Key

Format

CND

Description

TransID

ans..40

M

TransactionID which should be unique for each payment

RefNr

ns..30

O

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

UserData

ans..1024

O

If specified upon call, Paygate forwards the parameter with the payment result to the shop

Amount

n..10

O

Amount in the smallest currency unit (e.g. EUR Cent)

If the actually authorised amount differs from the requested amount this will be returned.

ErrorText

ans..128

O

Detailed Credorax error message.

Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

TokenExt

an..32

O

For recurring payments (RTF=I) the Token is transmitted for referencing the credit card data.

TransactionID

an..32

O

Transaction number from Credorax

Match

a1

O

Result of address check, for possible values see A3 AVS match parameters

Additional response parameters for credit card payments

Card processing - Credit Card Form

For more information about credit card processing via forms, please see chapter Credit Card Form (paySSL).

Card processing - Server-2-Server integration

For more information about credit card processing via server-to-server communication, please see chapter Server-2-Server Integration.

Capture / Credit / Reversal

For more information about capture, credit, reversal and credit card payment via POS terminals, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

PayNow

For more information about PayNow, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Batch processing via the interface

For more information about batch processing, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Paygate

Documentation (EN)

Dokumentation (DE)

Paygate Status