• DeutschEnglish

Chase Paymentech

Logo

Info

Chase Paymentech

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 Chase Paymentech

Besides the general parameters described above for the credit card connection, Chase Paymentech 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..11

O

TransactionID which should be unique for each payment

RefNr

ns..22

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

RTF

a1

O

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

ChDesc

an..21

O

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

Possible formats:

  • AN3*AN18 e.g. ABC*QWERTZ1234YX123ERT

  • AN7*AN14 e.g. ABC1234*QWERTZ1234YX12

  • AN12*AN9 e.g. ABC1234GFERT*QEW2Y3FGT

AccVerify

a3

O

AccVerify is available for SDK (Stratus) only, not for ISO8583 (Tandem).

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

Lodging

an2

O

Number of planned days of hotel accommodation

Textfeld1

as..12

O

Merchant's phone number.

If Textfeld1 is not submitted the value MerchantServicePhone from Madmin will be forwarded for the transaction.

Possible formats:

N3-N3-N4 e.g. 123-456-7890

N3-AN6 e.g. 123-456789

Contact data/Address verification (AVS)

FirstName

ans..28

O

First name of the customer (for AVS)

FirstName and LastName are combined in a field with the format „First name + „ *“ + Last name and forwarded together. The total content is truncated after 28 characters.

LastName

ans..28

O

Last name of the customer (for AVS)

FirstName and LastName are combined in a field with the format „First name + „ *“ + Last name and forwarded together. The total content is truncated after 28 characters.

AddrStreet

ans..30

O

Street name of the customer (for AVS)

Please note that AddrStreet and AddrStreetNr together may have 29 characters maximum.

AddrStreet and AddrStreetNr are combined with a space character between and forwarded together. The total content is truncated after 30 characters.

AddrStreetNr

ans..30

O

Street number of the customer (for AVS)

Please note that AddrStreet and AddrStreetNr together may have 29 characters maximum.

AddrStreet and AddrStreetNr are combined with a space character between and forwarded together. The total content is truncated after 30 characters.

AddrStreet2

ans..28

O

further street name (for AVS)

AddrZip

ans..10

O

Postcode of the customer (for AVS)

AddrCity

ans..20

O

Town/city of the customer (for AVS)

AddrState

a2

O

Code of the customer’s Federal State (for AVS)

AddrCountryCode

n3

O

Country code according to ISO-3166-1 numeric (3-digits) (for AVS)

Phone

ans..14

O

Customer telephone number in format AAAEEENNNNXXXX, wherein AAA=prefix, EEE=area code, NNNN=number, XXXX=direct line

PhoneType

enum

C

Reachability: D=Day; H=Home; N=Night, W=Work

Mandatory if Phone exists

sdFirstName

ans..25

O

First name in the delivery address

sdFirstName and sdLastName are combined in a field with the format „First name + „ *“ + Last name and forwarded together. The total content is truncated after 25 characters.

sdLastName

ans..25

O

Last name in the delivery address

sdFirstName and sdLastName are combined in a field with the format „First name + „ *“ + Last name and forwarded together. The total content is truncated after 25 characters.

sdStreet

ans..30

O

Street name in the delivery address

Please note that sdrStreet and sdStreetNr together may have 29 characters maximum.

sdStreet and sdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 30 characters.

sdStreetNr

O

Street number in the delivery address

Please note that sdStreet and sdStreetNr together may have 29 characters maximum.

sdStreet and sdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 30 characters.

sdStreet2

ans..35

O

Address addition in the delivery address

sdZIPCode

ans..10

O

Postcode in the delivery address

sdCity

ans..20

O

Town/city in the delivery address

sdState

a2

O

State/country in the delivery address

sdCountryCode

n3

O

Country code of the delivery address according to ISO-3166-1, numeric 3-digits

sdPhone

an..14

O

Telephone number in the delivery address in format AAAEEENNNNXXXX, wherein AAA=prefix, EEE=area code, NNNN=number, XXXX=direct line

sdPhoneType

enum

C

Reachability in the delivery address: D=Day; H=Home; N=Night, W=Work

Mandatory if sdPhone exists

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

O

TransactionID which should be unique for each payment

RefNr

ns..22

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

CodeExt

n..10

O

Original error code from Chase (if an error occurs), if agreed with Computop Helpdesk

Match

a1

O

Total result of an address verification: For possible values see A3 AVS match parameters

AmexTID

n..15

C

The TID value is assigned by the authorisation system of American Express.

The American Express authorisation system assigns a unique tracking number with which the accuracy of the authorisation data in the calculation data record is determined.

ApprovalCode

an6

O

Approval code, if agreed with Computop Helpdesk

Is issued by the bank or service facility. To be saved and supplied with the deposit business.

CountryStatus

enum

O

Status identification of the card-issuing country. Valid values: A – acceptable; B – blocked; S - suspect

RecurringPaymentAdviseCode

n2

O

Payment recommendation code. Valid values:

01 – new account information available. Call up new account information.

02 – Try again later. Transaction will be reversed in 72 hours.

03 – Do not retry. Request another payment method from the customer.

21 – Do not retry. The issuer has blocked repeated payment transactions.

" " - empty

AuthDate

n6

O

Date of originally approved transaction. Format: YYMMDD

cvcMatch

a..1

C

Result of CVC check. Possible values:

M = Match

N = No match

P = Not processed

S = Should have been present

U = Issuer unable to process request

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