• DeutschEnglish

GICC: Concardis, Payone, EVO Payments, American Express, Elavon, InterCard, SIX Payment Service, Paynetics

Logo

Info

GICC: Concardis, Payone, EVO Payments, American Express, Elavon, InterCard, SIX Payment Service, Paynetics

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 GICC: Concardis, Payone, EVO Payments, American Express, Elavon, InterCard, SIX Payment Service, Paynetics

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

REST

Format

CND

Description

RefNr

"referenceNumber": "..."

ans..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.

If RefNr is not submitted, the value of TransID will be used.

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

Notes:

For InterCard only alphanumeric characters are allowed, format an..30.

GICC --> Offline Capture --> GRRCN 4.01 EPA: RefNr displayed in field 13

Please use online capture as standard option and note the required EPA setting.

GICC --> Online Capture --> GRRCN 4.01. EPA: RefNr displayed in field 42

If the merchant would like use the Computop Settlement File, please get in touch with AMEX to configure/activate EPA format germany (EPAGR) as otherwise the RefNr value cannot be read out via GRRCN EPA format and written into the Computop Settlement File.

GICC --> Standard AMEX EPA-DE (EPAGR) or GRRCN EPA format: 30-characters alphanumeric

Note: The EPA format has changed and the RefNr is now shown at a different position.

GICC + DE-EPA Format: starting on position 98 = ReferenceNumber

Details on the EPA-format are provided to you by your acquirer.

OrderDesc

"order": {"description": "..."}

ans..768

M

Description of purchased goods, unit prices etc.

CreditCardHolder

"payment": {"card": { "cardHolderName": "..." }}

ans..60

O

Name of the card holder

RTF

---

a1

O

for repeat payments (subscriptions): I = Initial payment of a new subscription

R = Routine payment (Recurring)

ChDesc

an..30

O

Text printed on the customer’s credit card bill alongside the payee

AccVerify

"payment": {"card": { "<accountVerification": "..." }}

a3

O

AccVerify is available for AirPlus, American Express, B + S Card Service, Concardis, Diners, DZ Bank, EVO, Fiducia, Intercard, Paynetics, POS Transact, SIX and WGZ Bank only.

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

CountryCode

a2

O

Card holder information: Country

Textfeld1

ans..30

O

Card holder information: Name

Textfeld2

ans..30

O

Card holder information: City

ContractID

n..8

O

Further reference which can be used to retrieve the combination TerminalID/Contract partner number

Cryptocurrency

---

a..3

C

Used to flag a cryptocurrency purchase. Possible value "Yes".Notice: Possible only for credit card brands VISA, MasterCard, Maestro.

Contact data/Address verification (AVS)

AddrStreet

"billing": {"addressInfo": { "addressLine1": { "street": "..." }}}

a..50

O

Street name (for AVS)

AddrStreetNr

"billing": {"addressInfo": { "addressLine1": { "streetNumber": "..." }}}

ans..15

O

Street number for verification by American Express (for AVS)

AddrZip

"billing": {"addressInfo": { "postalCode": "..." }}

n..10

O

Postcode (for AVS)

AddrCity

"billing": {"addressInfo": { "city": "..." }}

a..40

O

Town/city (for AVS)

AddrCountryCode

"billing": {"addressInfo": { "country": { "A2": "..." }}}

"billing": {"addressInfo": { "country": { "A3": "..." }}}

a2/a3

M

Country code according to ISO-3166-1: it can be transmitted with two or three digits optionally – Format a2 / a3

AddrStreet2

a..32

O

Second street name (for AVS)

AddrStreetNr2

ans..5

O

Second street number (for AVS)

AddrZip2

n..5

O

Second postcode (for AVS)

AddrCity2

a..32

O

Second town/city (for AVS)

AddrChoice

n1

O

If you transmit 2 street numbers and postcodes, the AddrChoice parameter will determine which address is checked. AddrChoice=1 checks the first address, AddrChoice=2 the second address. (for AVS)

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

REST

Format

CND

Description

Match

a1

O

Total result of address check (American Express via GICC): For possible values see A3 AVS match parameters

TerminalID

an8

O

ID of the terminal

TransactionID

an..22

C

If transaction is approved and value returned by the acquirer: Transaction identifier returned upon approval. It must be submitted unaltered when subsequent authorization requests are related to a previous original request where this value is returned.

VUNr

n5..12

C

Contract partner number

TrxTime

an21

C

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

VU

n..

C

Contract partner number. The length depends on the acquirer.

If you want to have the acquirer contract partner number within the reponse, please contact Computop Helpdesk which can activate this response function for you.

AQ

an5

C

Acquirer shortcode.

If you want to have the acquirer name within the reponse, please contact Computop Helpdesk which can activate this response function for you.

Possible values: AMEX=AME, Elavon=CKS, Concardis=CON, Payone=BUS, Paynetics=PNS, Six Payment=SIX, EVO Payments=EVO, Intercard=INT; SIXAT, SIXPG, Adyen

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