• DeutschEnglish

EVOxml

Logo

Info

EVOxml

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 EVOxml

Besides the general parameters described above for the credit card connection, EVOxml 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

MARP

a3

O

Not with 3-D Secure: to activate MARP at EVO Payments International (Maestro Advance Registration Program™) <yes> or <no>

CustomerID

an..20

O

Customer number: Number to identify the customer

RefNr

ans..20

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, ...).

(only capitals allowed)

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

OrderDesc

an..30

O

Description of purchased goods, unit prices etc.

RTF

a1

O

For repeat payments (subscriptions) (Recurring):

I: Initial payment of a new subscription

R: Routine payment (Recurring/Subscription)

S: Recurring installment payment (Installment)

For unscheduled payments (e.g. UCOF or via App):

E: Initial payment with storage of payment data

C: Customer initiated payment (CIT) with stored payment data (1-click-shopping)

M: Merchant initiated payment (MIT) with stored payment data (UCOF)

ChDesc

an..30

O

Dynamic text component of the posting text of credit card transactions

Contact data

FirstName

ans..30

O

First name of the customer (for Fraud Screening optional)

LastName

ans..30

O

Last name of the customer (for Fraud Screening mandatory)

AddrStreet

an..46

O

Street name of the customer (for Fraud Screening mandatory)

AddrStreetNr

an..35

O

Street number of the customer (for Fraud Screening optional)

AddressAddition

ans..6

O

Address addition (for Fraud Screening optional)

AddrPOBox

n..35

O

Post office box (for Fraud Screening optional)

AddrZip

an..9

O

Postcode of the customer (for Fraud Screening mandatory)

AddrCity

an..40

O

Town/city of the customer (for Fraud Screening mandatory)

AddrDistrict

ans..40

O

County/region (for Fraud Screening optional)

AddrState

a2

O

Code of Federl State of the customer (for Fraud Screening optional)

AddrCountryCode

a2

M

Country code according to ISO-3166-1, alphanumeric 2 chars (for Fraud Screening optional)

eMail

an..80

O

Email address of the customer (for Fraud Screening mandatory)

Phone

ans..20

O

Phone number of the customer (for Fraud Screening mandatory)

MiddleName

ans..30

O

Middle name

Salutation

ans..10

O

Salutation e.g. Mr or Mrs, compulsory field for fraud screening

Title

ans..20

O

Title, e.g. Dr. or Prof.

CompanyOrPerson

a1

O

F=Firm, P=Person, compulsory field for fraud screening

DateOfBirth

n8

O

Date of birth in the format YYYYMMDD

Gender

a1

O

Gender: <m> male or <f> female

WorkPhone

ans..20

O

Telephone number at the work place

Fax

ans..20

O

Fax number

E-Mail

ans..80

O

E-mail address

NewCustomer

ans..5

O

New customer: Yes or no

DateOfRegistration

ans8

O

Date of registration (YYYYMMDD)

SocialSecurityNumber

ans..9

O

Social security number

DrivingLicenceNumber

ans..37

O

Driver's licence number

Delivery data

sdFirstName

an..30

O

First name in the delivery address

sdLastName

ans..25

O

Last name in the delivery address

sdMiddleName

ans..30

O

Middle name in the delivery address

sdStreet

an..46

O

Street name in the delivery address

sdStreet2

an..46

O

Address addition in the delivery address

sdZip

an..9

O

Postcode in the delivery address

sdZIPCode

an..9

O

Postcode in the delivery address

sdCity

an..40

O

Town/city in the delivery address

sdState

a2

O

State/country in the delivery address

sdCountryCode

a2

O

Country code of delivery address according to ISO-3166-1, alphanumeric 2 chars

sdeMail

an..80

O

E-mail address of the delivery address

sdPhone

ans..20

O

Telephone number in the delivery address

sdWorkPhone

ans..20

O

Second telephone number / telephone number at the work place in the delivery address

Parameters for AVS (Address verification)

CreditCardHolder

ans..60

O

Name of the card holder (for AVS mandatory)

chStreet

an..46

C

Street name of the credit card holder (for AVS mandatory)

chHouseNumber

an..35

O

Street number of the credit card holder (for AVS optional)

chPOBox

an..9

O

Post office box of the credit card holder (for AVS mandatory)

chCoField

an..40

O

Bulk recipient name of the credit card holder (for AVS optional)

chZipCode

an..9

O

Postcode of the credit card holder (for AVS mandatory)

chCity

an..40

O

Town/city of the credit card holder (for AVS mandatory)

chDistrict

an..40

O

Urban district of the credit card holder (for AVS optional)

chState

an2

O

2-digit code of the Federal State of the credit card holder (only for USA) (for AVS optional)

chCountryCode

a2

O

Country code of the credit card holder in the format ISO-3166-1, alphanumeric 2-digits (for AVS mandatory)

All following parameters refers to the bought flight ticket

TicketNr

an..15

C

Reference to the bought flight ticket

PassengerName

an..49

C

Name of the flight passenger

FlightDate

an..5

C

Flight date. Format: DDMMM (e.g. 15MAY, 01NOV, 30JUN)

Origin1

an..5

C

International code for the departure airport

Origin2

an..5

C

International code for the departure airport

Origin3

an..5

C

International code for the departure airport

Origin4

an..5

C

International code for the departure airport

Destination1

an..5

C

International code for the arrival airport

Destination2

an..5

C

International code for the arrival airport

Destination3

an..5

C

International code for the arrival airport

Destination4

an..5

C

International code for the arrival airport

Carrier1

an..4

C

International code for the airline company

Carrier2

an..4

C

International code for the airline company

Carrier3

an..4

C

International code for the airline company

Carrier4

an..4

C

International code for the airline company

fsSkip

an..4

O

„YES“ = Skip the Fraud Screening.

Overrides merchant configuration

fsIgnore

an..6

O

„YES“ = Ignore the Fraud Screening result.

Overrides merchant configuration

fsReject

a1

O

Call up control of Fraud Screening

C: Accept transaction in the event of CHALLENGE

E: Accept transaction in the event of ERROR

avsSkip

an..4

C

„YES“ = Skip AVS

avsIgnore

an..6

C

„YES“ = Ignore AVS result

avsReject

a..7

C

List of result codes which reject the transaction

NI: Decline only if postcode and street do not match

ABNI: Decline: Street does not match or street and postcode do not match.

WZPNI: Decline: Postcode does not match or street and postcode do not match.

ABWZPNI: Decline: At least one of the elements AddrStreet and AddrZipCode does not match.

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

RefNr

ans..20

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, ...).

(only capitals allowed)

ErrorText

ans..128

O

Error text from EVOxml, if agreed with Computop Helpdesk

FSMatch

an..9

O

ACCEPT: Accept transaction, low risk

DENY: Deny transaction, high risk

CHALLENGE: Check transaction additionally, risk not clear

ERROR: Internal error

AVMatch

a1

O

Result of address check, see A3 AVS match parameters

TrxTime

an21

M

Time stamp of transaction in the format dd.MM.yyyy HH:mm:ssff

AQ

an3

M

Acquirer shortcode

AuthCode

ans..6

M

Acquiring Bank's authorisation code

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